Add MSP support for led profile and status

[haslinghuis]

Finally add support for betaflight/betaflight#7491

Added a flag indicating the level of ledstrip support (to allow improved Configurator behavior) along with support for reading/setting the current ledstrip_profile [RACE, BEACON, STATUS]

ledstrip support flag [STATUS] is as follows:
0 = basic ledstrip available
1 = advanced ledstrip available

In follow up we could do something useful with this.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[nerdCopter]

• approving untested

[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!

[ctzsnooze]

The distinction between basic and complex profiles is no longer relevant.
The whole LED code needs to be refactored without that distinction.
We should not change MSP to add a new element now, because it is likely to be unnecessary when the LED code is properly modernised.

[haslinghuis]

This is not a change. Just implementing current firmware behavior. Any changes to that can be done in subsequent PR.

[blckmn]

AUTOMERGE: (FAIL)

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