BLE Support

[Scavanger]

Replaces #7783

[stronnag]

This does not require an MSP version bump; we didn't do that for the introduction of MSP2.

[DzikuVx]

@Scavanger this is a no-go. We can not change the current MSP frame to have a completely different structure.
Instead of changing MSP2_INAV_LOGIC_CONDITIONS let's do the following:

1. Leave MSP2_INAV_LOGIC_CONDITIONS unchanged
2. Add MSP2_INAV_LOGIC_CONDITIONS_SINGLE frame
3. Switch configurator to use MSP2_INAV_LOGIC_CONDITIONS_SINGLE

[stronnag]

@Scavanger , couple of questions / comments.

• cli_delay is ephemeral. It is not saved by CLI save. Is this deliberate, if so why? I think this will cause confusion.
• In any case, why not a set paramer. Then it could be set from the configurator / MSP clients using MSP2_COMMON_SET_SETTING ?
• cli_delay is useful for other use cases than BLE (e.g. dump works with GCC 11.2 compiled firmware, even if this is band-aid rather than a cure).

[Scavanger]

@stronnag
cli_delay is only a workaround for some BLE adapters, it is not intended to be used by the user.
It makes no sense to save it, it would have to be reset when exiting CLI mode or the next CLI session would have to check again whether there is a BLE connection, otherwise the delay would be used unnecessarily, e.g. for a USB connection.
I think that would complicate everything.