- override by vehicle type
- override by firmware type

C++2003 didn't had variadic templates so different number of
arguments must have been already implemented in the templates
and since it's impossible to get the amount ot different methods
that paople write, a variadic template was neede.

now we can connect signal / slots with 6+ arguments.
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>

Refactored PX4 radio config to work with both PX4 and APM

- New mission command editor dialog
- New MissionCommands toolbox object to get command info
- Added APM mission item set

- 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