Flasher tab: remember last user selected radio protocol

[limonspb]

Flasher tab.
Stores the last radio protocol selected by the user into localStorage.
Sets radio protocol dropdown to the last selected value (if value is present in the list, otherwise shows default value)
Update: everything is ignored if buildkey is present = radio protocol is loaded from buildkey.

[blckmn]

AUTOMERGE: (FAIL)

• github identifies PR as mergeable -> PASS
• assigned to a milestone -> PASS
• cooling off period lapsed -> PASS
• commit count less or equal to three -> PASS
• Don't merge label NOT found -> PASS
• at least one RN: label found -> FAIL
• Tested label found -> FAIL
• assigned to an approver -> FAIL
• approver count at least three -> FAIL

[haslinghuis]

This should work for 4.4.3+: betaflight/betaflight#12876

[haslinghuis]

@limonspb as this code won't be needed for 4.5.0 anymore would like some semver conditions added - but actually we should reject the change:

• it would already be fixed in 4.4.3 in #12876
• PR only works if using one specific type of receiver.
• in a mixed environment this only adds extra maintenance.

Shame there is no #USE_IF_IAM_NOT_LAZY macro 😛 🙈

[limonspb]

@limonspb as this code won't be needed for 4.5.0 anymore would like some semver conditions added - but actually we should reject the change:

• it would already be fixed in 4.4.3 in #12876
• PR only works if using one specific type of receiver.
• in a mixed environment this only adds extra maintenance.

Shame there is no #USE_IF_IAM_NOT_LAZY macro 😛 🙈

lots of people will be upgrading from 4.2 4.3, from 4.4.0, from 4.4.1, and from 4.4.2. Heck, there are people still on 4.0 lol.
This PR does not change anything, if you are already at 4.5 or 4.4.3, but it helps to others who upgrading from older versions with multiple drones. Thats the only purpose.
If someone has drones with different receivers - they need to select protocol either way. Some people (or most of them?) got same RXes on multiple drones, so at least we can save a couple of clicks for them :)

[haslinghuis]

but it helps to others who upgrading from older versions with multiple drones.

assuming they all have the same receivers. Soon everyone will at least be flashing 4.4.3 :)

@McGiverGim what's your opinion?

This PR assumes configurator will be released before 4.5.0. Sure have no problem with that but it should be coupled at least with 4.4.3 and introduce a feature freeze (unless its 10.9.1). Rather have some more time to test nightly builds for now.

4.5.0 should not take too long as products are already out there.

[limonspb]

but it helps to others who upgrading from older versions with multiple drones.

assuming they all have the same receivers. Soon everyone will at least be flashing 4.4.3 :)

@McGiverGim what's your opinion?

This PR assumes configurator will be released before 4.5.0. Sure have no problem with that but it should be coupled at least with 4.4.3 and introduce a feature freeze (unless its 10.9.1). Rather have some more time to test nightly builds for now.

4.5.0 should not take too long as products are already out there.

thats overestimation that everyone will be on 4.4.3 :) And this PR does not change anything for 4.4.3+ people.

[McGiverGim]

@McGiverGim what's your opinion?

I think is useful. In my case, for example, I'm on FrSky FPORT, that is not selected automatically. I have few drones, but if someone has some dotzens then it's useful. The same can be done for some "extra" flags, like MAG or similar.

[haslinghuis]

@limonspb please rebase so we can merge this.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[github-actions]

Do you want to test this code? Here you have an automated build:
Betaflight-Configurator-Android
Betaflight-Configurator-Linux
Betaflight-Configurator-macOS
Betaflight-Configurator-Windows
WARNING: It may be unstable and result in corrupted configurations or data loss. Use only for testing!