Forcing QGC to use Mavlink V2 if vehicle supports it.

Also added new FirmwarePlugin::brandImage support

_finalize methods need information which is not available if all you
have is a mavlink_message_t

Includes ability to load params

- GeoFence support comes from plugin
- Circle fence support
- Better param support

Move battery.percentRemainingAnnounce to Qml Global

The static Fact was causes problems with Qml

Numbering on motor command is wrong (or strange), so wrong motors spin
when using sliders

* Deal with missing parameters on Solo

* Fix trigger set

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>