Also distinguish Emergency Stop better

The idea here is to prevent people from accidentally flashing the wrong firmware

* Added support for sat count to Sensors check control

* QGCCheckListItem -> PreFlightCheckButton
* CheckList -> PreFlightCheckList

Automated preflight checklist: Initial commit. Note that this requires an autopilot firmware that writes the respective health flags in the SYS_STATUS mavlink message

The build system will look for src/Airmap/Airmap_api_key.h
If it find is, it will used the provided API key and client ID for Airmap.
That file should provide two strings:
static const char* kAirmapAPIKey = "key data";
static const char* kAirmapClientID = "id data";

Local builds, without these will have no Airmap support by default (users can always enter their own within the Airmap settings panel).

For much better performance

This forces a commit on any uncommitted TextFields

Added (UI) support for vehicles exposing more than one camera.

Cleaning up old vehicle manager and getting it ready to actually provide services for a vehicle (flight management)
Added submit flight plan
Added update flight plan
Disable flight features as these don't seem to be quite working (values must be initialized and validated before submission as backend doesn't validate and the objects don't initialize their members)

Create a "Dead Mouse Area" control to eat mouse events underneath desired area. This is to prevent mouse events from leaking through controls underneath the area.
Replace original "NoMouseThroughRectangle" as this is more versatile.
Prevent mouse through events from leaking underneath the Fly View tool strip.

Adding missing qgcView to QGCMapPolygonVisuals instance in SurveyMapVisual.qml

Permit refactoring
QGCButton tweaks

Make all argument to AirMap queries based on what the screen shows (bounding rectangle and/or radius), respecting the limits imposed by AirMap.

AirspaceManager is now exposed by QGroundControlQmlGlobal instead of Vehicle (available all the time)