During tests, if the airframe was configured to be an 'X' type
we showed just 'X' on the airframe type. It's correct but a
single letter - specially an X - made users think that it was
a error code, not the airframe name. So, because of that, also
show the vehicle type - a wrong value, but elucidative for users.
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

I removed some needed headers from a top level file which then causes a
ripple effect downstream

Removed incorrect Vehicle.altitudeWGS84

Plumb through initial object mode on Vehicle

Windows OS doesn’t disconnect port when you pull plug on USB. This
caused all sorts of problems with previous logic. New logic handles
this correctly.

- 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