New VehicleLinkManager implementation

More flight mode, vtol mode, armed into main status

Camera brand/model support. Use canonical camera names in Plan files.

supportedMissionCommands is vehicle class sensitive

Remove buggy usage of vehicleYawsToNextWaypointInMission

Support for Vehicle and Firmware classes

New QGCFileDownload support for bit.ly style redirects and file name

Support parameter meta data coming from COMPONENT_INFORMATION as well as old system

FirmwarePlugin::adjustOutgoingMavlinkMessageThreadSafe not required to be thread safe

LinkInterface and Vehicle uses mutexes to synchronize writing bytes to the link instead of queued signals

Re-architect toolbar for better customization capabilities. Also use less real estate.

App messages now use simple modal message dialogs. Vehicle messages continue to use non-modal popup.

Mavlink terrain protocol support

Reorder indicators

Reorder toolbar indicators

Plugin'ized follow me support

Remove firmware version type since official always

Instead of trying to keep a vehicle type within the FirmwarePlugin instance, pass the vehicle to the function so it can query the type that way.

Smart RTL support

Revert the camera names to their original names to avoid messing up old plan files, which use the camera name string to match the camera to the plan.

Remove the concept of reserved buttons for manual control

Add gotoFlightMode method

Only version check stable builds

FirmwarePlugin: Issue a warning upon connecting if the firmware in use is not using a stable release