This way:
* GCS location is shown
* It follows same centering semantics of FlightMap
* Note: Vehicle is not shown

Used to display items associated with Flight Plan on Map

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

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

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

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

Switch test from 8.8.8.8:53 to "www.github.com:80"

Radio upgrade: Point updater to a binary which is fully MAVLink 2.0 enabled, including radio status.

This is important to avoid having QGC hijack links that are active (we read 2000 bytes!) but are definitely not MAVLink. This can have nasty side-effects, e.g. if we would talk to an LTE modem in a laptop or alike.

Switch only to MAVLink 2 on first connected link. Fall back to v1 if two links to the same vehicle are connected and one can only do v1

This extension introduces a complete version handshake mechanism which will detect wether the vehicle AND the complete link / routing infrastructure support MAVLink 2. If they do, QGC will switch to the highest protocol version supported by all connected vehicles. If a new vehicle connects, it will re-negotiate the highest possible version. This means that we error on the side of compatibility, which later can be easily changed.

* If new Survey is set to altitude fixed value then use mission default
altitude
* If the user applies a new altitude to the entire mission change
surveys to fixed altitude and apply altitude

This way if the user switches away from manual the altitude is preserved