Android done.

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>

Change all text to have a qsTr call, this way it will
call the right translated text when needed.

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

Takes less real estate and flows better and small displays

This commit introduces the APM Airframe configuration. The interface
is the same as the PX4 one, but the way we deal with the uas is a bit different

Since the APM stack doesn't provide a xml with airframe definitions a
new one was created by hand with only the values that we need, wich will
trigger a download of the parameters file from the mavlink github

Now it correctly handles the FRAME variable and it's faster
regarding the download of the parameters for each type of Frame.

Only show Airframes for ArduCopter, not for ArduRover nor ArduPlane

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

Passing parameters QVariantMap across C++ boundary was causing crashes
in Qt due to Qml array bugs. Referencing same Fact* across Qml boundary
in multiple QQuickWidgets caused jScript GC to crash.