Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

This makes VehicleComponents reusable from core plugin without
requiring override of prerequisiteSetup

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

Also, added a missing method on AutoPilotPlugin as a public
pure virtual method (the inheritances already implemented it as a
slot, so the new Signal syntax didn't worked because the base class
didn't had that method)
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

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>

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

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

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.

QGCUASParamManager and friends are replaced by FactSystem

More consistent with Qml usage pattern

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.

Also, uas is kept in object

- properties now hand off of main “autopilot” object in qml
- Added support for summary items through qml

This way you don’t need to know parameter set ahead of time.

Plus a large number of other changes to allow for orderly shutdown of
objects without crashes or asserts. This is need for unit tests to
create/delete global state around every test.

Allows parameter access from QML among other things