Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

- Pervasive change to automatically connect to known board types
- Lots of additional changes along with this:
- More exposure of objects/properties to Qml
- Much restructuring in LinkManager and LinkManager clients

- Pervasive change to automatically connect to known board types
- Lots of additional changes along with this:
- More exposure of objects/properties to Qml
- Much restructuring in LinkManager and LinkManager clients

- Pervasive change to automatically connect to known board types
- Lots of additional changes along with this:
- More exposure of objects/properties to Qml
- Much restructuring in LinkManager and LinkManager clients

Instead us a Toolbox concept which hangs off of QGCApplication

This is in preparation for full Qml main window

- Delete all old map code

- Moved all MavManager functionality to Vehicle
- Updated all code to use Vehicle instead of MavManager
- Removed MavManager

- MultiVehicleManager is a Qml friendly replacement for UASManager
- Vehicle is a replacement for both UAS and AutoPilotPlugin

- FirmwarePlugin is the new place for code which is specific to
firmware flight stack
- FirmwarePlugin currently supports flight mode apis
- Modify code to use new FirmwarePlugin support

Everything is now based off of default font pixel size

Also adding a constant for the font size in SensorComponent.

If Facts are referenced from FactPanelController, we need to reference
count the AutoPilotPlugin such that it doesn’t get destroyed until
after the FactPanelController is destroyed.

Sorting source and headers while at it.

Initial rendering of Waypoints

QGCUASParamManager and friends are replaced by FactSystem

I forgot an extra argument for debugging (and didn't have WarningsAsErrorsOn properly set)
No idea how that emit qDebug ended up in there.

Removed left over debug message.