FrSky telemetry update
Replace profile.activate and rcOptions with
profile.modeActivationCondition and rcModeActivationMask.

Implementation of using and setting modeActivationConditions is missing.
First cut of code that passed the unit tests for mod activations,
however it uses / operations and doesn't handle the case where the
channel value is on the boundary between two ranges.
Handle channel boundaries better.
More efficient, less code, easier to understand.
Update the cli AUX command to take range parameters - see docs/Modes.md
Updating baseflight migration note regarding aux configuration.
Cleanup table formatting of modes.
Fix setting of upper limit for mode ranges in cli.
Determine with an aux range is used to arm.
Cleanup some aux range defines and comments.
Add two new MSP commands to get ALL mode ranges and to set individual
mode ranges.
Use permenant mode ids in MSP_MODE_RANGES and MSP_SET_MODE_RANGE.
Fix range check problem for first mode range index.
Ensure mode flags are correctly generated after the switch to a bitmask
for activated modes.
Use permenant id for MSP_SET_MODE_RANGE.
Bump EEPROM version for mode range support.
Latest binaries with mode range support.
Add MSP capability bit so clients can detect Cleanflight and use an
appropriate API.  Renumber some cleanflight specific MSP commands,
Cleanflight will use the range 32-63 for new MSP commands.
Add MPU6500 SPI driver.  Move sensor initialisation defines into target
specific headers.
Initial stab at supporting MPU6500.
Make I2C driver fail gracefully when I2C hardware hasn't been initialized (on boards w/o I2C sensors)