update pid_tuning page for 4.3

Fix sliders disable input

Verify target has all addresses found in the hex file instead of
verifying the size.

As noted in PR betaflight#2512 simply verifying the size of the hex file is not
extensible and is not how hex files are designed to be used.

A hex file can contains many non-contiguous blocks of data.

This also supports targets with any partition layout.

Additionally, this provides a more flexible way of providing hex files
which can now contain data for non-contiguous blocks, e.g. firmware +
config or firmware + osd fonts.

Fix pre-existing code-smells.

Indicate inactive dyn notch if looprate less 2k

don't change filter type when moving filter slider

Presets: remove cache for fetch

Update github issues templates

Fix Port Detection using VID/PID

Add option for manufacturers and developers

fix integrated yaw usage

move code to pidtuning.js

fix tuningsliders

disable only if rpy

Fix filter slider update

Fix lowpass 1 handlers

Put things back

Restore Initial Settings

Fix PID rows updating

Work on PID

Fix PID copy

Remove PID validation

Apply new MSP

FW sliders: fix gyro and dterm ON/OF toggles

FW sliders for 4.2: Mark's diff file applied

FW Sliders for 4.2: Fix infinity for PD ratio and fix PD gain slider adjustin only D

FE Sliders for 4.2: fixing legacy filter and PID sliders - bringing back old logic

FW Sliders: bringing back SetDirty for the correct profile select blocking

Fix slider calculation

Remove MSP_APPLY*

Fix legacy

Revert CSS for PID tab

Move Filter Mode element in UI

Remove bitflag

Remove apply byte

FW sliders: symmetrical MSP commands

Fix saving gyro lowpass 1 disable

FW sliders: fix dterm dynamic LPF after enabling it

FW sliders: fix enabled input field background

FW Sliders: fix when loading PID tab with non-default expert sliders in non-expert mode

Author: ctzsnooze

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,27 @@
+---
+name: Bug Report
+about: Create a report to help us fix bugs in Betaflight Configurator
+labels: "Template: Bug"
+---
+<!-- This is a template that you must fill. If not, the message will be closed. So don't erase any subtitle in this template (they start with ###)
+and complete all of them -->
+
+### Describe the bug
+<!-- A clear and concise description of what the bug is. -->
+
+### To Reproduce
+<!-- Steps to reproduce the behavior -->
+
+### Expected behavior
+<!-- A clear and concise description of what you expected to happen. -->
+
+### Setup
+<!-- Specify the version of the configurator (as displayed in the app) -->
+- Configurator version:
+
+<!-- If this bug is related to a specific flight controller and/or configuration please specify it here. Create a diff and post it here in a code block. Put (three backticks) at the start and end of the diff block (instructions  on how to do a diff: https://oscarliang.com/use-diff-not-dump-betaflight/) -->
+```
+PASTE THE OUTPUT OF 'diff' HERE
+```
+
+<!-- Add any other context about the problem that you think might be relevant here. -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Configuration and other support questions
+    url: https://github.com/betaflight/betaflight#support-and-developers-channel
+    about: Official Slack chat channel and Facebook group about Betaflight
+  - name: Hardware Issues
+    url: https://github.com/betaflight/betaflight#hardware-issues
+    about: What to do in the case of hardware issues

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,21 @@
+---
+name: Feature Request
+about: Suggest an idea for for a new feature for Betaflight Configurator
+labels: "Template: Feature Request"
+---
+<!-- This is a template that you must fill. If not, the message will be closed. So don't erase any subtitle in this template (they start with ###)
+and complete all of them -->
+
+<!-- Please note that feature requests are not 'fire and forget'. It is a lot more likely that the feature you would like to have will be implemented if you keep watching your feature request, and provide more details to developers looking into implementing your feature, and help them with testing. -->
+
+### Is your feature request related to a problem? Please describe.
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+
+### Describe the solution you'd like
+<!-- A clear and concise description of what you want to happen. -->
+
+### Describe alternatives you've considered
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+
+<!-- Add any other context or screenshots about the feature request that you think might be relevant here. -->

.github/issue_template.md

@@ -255,11 +255,6 @@
     text-align: right;
     border: 1px solid var(--subtleAccent);
     border-radius: 3px;
-    background-color: #f9f9f9;
-}
-
-.tab-pid_tuning .subtab-pid table input:disabled {
-    background-color: #dddddd;
 }
 
 .tab-pid_tuning .subtab-filter table input,
@@ -906,7 +901,13 @@
 }
 
 .tab-pid_tuning .subtab-pid .cf_column {
-    min-width: 600px;
+    min-width: 450px;
+    flex: 1.3;
+}
+
+.tab-pid_tuning .subtab-pid .cf_column_right{
+    min-width: 300px;
+    margin-left: 15px;
     flex: 1;
 }
 
@@ -1011,6 +1012,15 @@
         width: 100%;
     }
 
+    .tab-pid_tuning .subtab-pid .cf_column_right {
+        min-width: 100%;
+        margin-left: 0px;
+    }
+
+    .tab-pid_tuning .note-button td:first-child {
+        width: 60%;
+    }
+
     .tab-pid_tuning .spacer_left {
         width: 100%;
     }
@@ -1058,4 +1068,10 @@
     .tab-pid_tuning .tuningPIDSliders .pid_titlebar th:nth-child(2), .tab-pid_tuning .tuningFilterSliders .pid_titlebar th:nth-child(2) {
         width: 20%;
     }
+
+    .tab-pid_tuning .pid_titlebar th div .xs {
+        text-overflow: ellipsis;
+        overflow: hidden;
+        white-space: nowrap;
+    }
 }