New VehicleLinkManager implementation

* Flight modes still not implemented. Waiting on message change.
* Also includes various cauterization of UI things which should not be
available on high latency link.

This extension introduces a complete version handshake mechanism which will detect wether the vehicle AND the complete link / routing infrastructure support MAVLink 2. If they do, QGC will switch to the highest protocol version supported by all connected vehicles. If a new vehicle connects, it will re-negotiate the highest possible version. This means that we error on the side of compatibility, which later can be easily changed.

Use component id from heartbeat

Includes ability to load params

- Also fix vehicle selector dropdown in toolbar

- 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

- Delete all old map code

- select active vehicle
- arm/disarm
- select flight mode

- 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