ADSB server support provided through new ADSBVehicleManager implemenation

A contextual Land/RTL tool. Better waypoint line calc.

Rework Mission Complete dialog for correct Resume Mission on ArduPilkot

Hide pre-arm message when vehicle arms

Fix bad merge

Disable Pause if fixed wing on approach

Remove deprecated Resume Mission action

Fix scoping of visibility changes

Fix Toolstrip positioning

Better flight trajectory point algorithm

Plugin'ized follow me support

Directions arrows in Fly View

Hide waypoint indicators unless they are really needed

Add Terrain toggle to MapScale control

Disable video workaround for gstreamer crashes

Move Log Replay bar to Window footer

Zoom buttons move to MapScale control

Fix list scrolling

Toggle Rally Point insertion on/off.
Highlight current Rally Point and current Waypoint.
Use tab bar instead of a row of radio buttons for selection (Mission, Fence, Rally).
Fix QGCHoverButton to handle proper checked state toggle.
Get rid of the many arrays used to define behaviors for the ToolStrip. They are now all defined within its model.
Fixed color for disabled text within ToolStrip (it was invisible)

This helps with other IDE's that handle CMake better than QMake

Fix : COGAngle indicator was shown everytime, fix isCOGAngleOK

Configurable Go To Location max distance

Configurable maximum distance on Go To Location

When dealing with an automatically configurable video stream, handle the video source automatically as well.

By default the Instrument Panel is the one from master,
It can be switched to alternate version by a checkbox in General Settings/Fly View

- Rename QGCInstrumentWidgetAlternate to QGCInstrumentWidget as it's now the default version
- Select  QGCInstrumentWidget as instrumentLoader source

Update all files that use a QML Menu item to QtQuick.Controls 2.4 to solve the issue of a menu showing up in random places on Android.

Move PreflightCheckList to custom builds only. The model, which used to be implemented within BuiltinPreFlightCheckModel is now within the control itself. It is up to the implementer to define a proper model.