GCS-Fix crash when clicking second "default" scope config
GCS-telemetryscheduler fix frozen bar coloration

#524
GCS-Fixed memory leak on serialplugin

#422
GCS-fixed redefined mixer types enum in vehicle config.

Now uses the enums from the MixerSettings UAVO.
Not properly tested.
Fixes #303
GCS-serial plugin memory leak fix - moved var setting to inside loop

Where it belongs
GCS-vehicle config-deleted commented code, and fixed bug

String list was being set with wrong list.
f3 i2c: fix first transfer for callbacks as well
f4 pios_i2c: removed useless sempahore action for callback transfers
f3 pios_i2c: removed useless semaphore action for callback transfers
f4 pios_i2c: refactored code to remove i2c_adapter_callback_handler
f3 pios_i2c: refactored code to remove i2c_adapter_callback_handler
f4 pios_i2c: refactored usage of portEND_SWITCHING_ISR
f3 pios_i2c: fixed formatting
f4 pios_i2c: fixed formatting
GCS-Small formatting fixes on serialplugin and telemetryscheduler
ppm: only hold off supervisor when we have sane PPM frames

Prior to this, the supervisor was held off any time we saw
valid frame pulses, even if the frame wasn't otherwise sane.

This causes a particular issue on Graupner Rx's when they
trigger failsafe mode (ie. when the Tx signal goes away).
These Rx's output a 50Hz square wave which will look to the
PPM code like a continual series of frame pulses with zero
valid channels.  This was previously enough to hold off the
supervisor and resulted in the PPM code holding the last good
value on all of its inputs.  This entirely invalidated the
failsafe behaviour on the Graupner Rx.

The 50Hz square wave should now be properly detected as an
invalid frame (zero channel pulses) and should allow the
supervisor to declare all channels as being in the TIMEOUT
state so the FC can activate its own failsafe mode.
On Linux, the file dialog does not automatically append a
file extension. This ensures that the filename is refused
unless an extension is given.
ppm: reduce number of frames required for declaring frame lock
ppm: mark Fresh flag as volatile

The Fresh flag is modified by both the timer interrupt
callback as well as the supervisor callback.  Due to
both of these being in callbacks, there isn't really any
risk of the compiler optimizing out the load but this
really is a volatile flag.
ppm: mark Tracking flag as volatile

Modified by both supervisor callback path and timer interrupt.