supportedMissionCommands is vehicle class sensitive

Remove buggy usage of vehicleYawsToNextWaypointInMission

Support for Vehicle and Firmware classes

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

FirmwarePlugin::adjustOutgoingMavlinkMessageThreadSafe not required to be thread safe

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

Mavlink terrain protocol support

Drive Plan view ROI support from firmware capability bits

Allow plugin to add flight modes to joystick button actions

Plugin'ized follow me support

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.

Clean up parameter meta data version methods to match spec

Smart RTL support

Remove the concept of reserved buttons for manual control

Add gotoFlightMode method

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

Buggy and no longer needed

Needed to support different indicators for advanced mode