Instead us a Toolbox concept which hangs off of QGCApplication

When you selected via the Menu to go to Fly Mode, the QML
toolbar didn't followed the option, and if you selected
via the menu to go to all the three possible views (setup,
fly and plan) the menu would be all-selected.

This tries to keep consistency of things.
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

Since the Static const char * items are private and nothing
should access them besides the MainWindow class, declare
them inside of the .cpp file with static linkage, this way
a few good things happen: they are not exported as symbols
to any other class (not even with private linkage) and also
if we need to add a new one, on the .cpp, the only compiled
file will be the cpp, instead of the tons of files that include
mainwindow.h
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

This reverts commit 86f29adf.

This is in preparation for full Qml main window

- Delete all old map code

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

Too complicated supporting both modes as editor becomes more complex

These use OpenGL implementation which prevented moving to ANGLE
support. Since they are rarely used they are being remove instead of
being upgrade.

These use OpenGL implementation which prevented moving to ANGLE
support. Since they are rarely used they are being remove instead of
being upgrade.

Plus lots of other cleanup

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

Sorting source and headers while at it.