Make AirMapController as part of a Vehicle rather than a creatable QML instance. This is ultimately linked to a vehicle and not the view. Eventually a lot of the code currently in AirMapManager will have to come here as well so the data persists with a vehicle. AirMapManager should only handle the global aspects.
Added a temporary indicator right below the toolbar. It's only visible if a permission (of any kind) exists. I need to understand better how this works before coming up with a more permanent solution.
Restored toolbar to its original state (brand logo and whatnot)

Added AirMap settings (SettingsGroup)
Added AirMap settings block to General Settings
Create macros to deal with the tedious repetitions within SettingsGroup
Removed old, hacked in setting for AirMapKey
Remove a few of the tons of build warnings

This includes polling for a flight permission.
The steps are:
- get pilot id (new API requires to provide it, even though it does not
  make much sense)
- create a flight plan
- call the briefing (to check if SITA registration id's are valid)
- call the submit -> returns the actual flight id
- poll on the briefing until the flight gets approved

Since there can only be one flight, on startup, we list the pilot's flights
and end the one that ends in future

- start telemetry if there's a valid flight id and the vehicle armed
- only the Position message is sent for now

Requires protobuf to be installed on the build system

Source: https://github.com/kokke/tiny-AES128-C
License: public domain

This is just to test, will need much better integration

This reverts commit cc1fa959.

Fixes #5787

Support ROI tool button in WaypointsOnly mode

Maps: added Eniro as map provider (Norway,Sweden,Finland,Denmark,Poland)

Fix position updates on Android

Adding access to the vehicle hobbs meter

Firmware upgrade use QSerialPort