Add support to Px4 parameters metadata #2610
Description
From Hamish:
YOu are correct. QGC uses the MAVLink component metadata protocol to get the URI of the component metadata file, which in turn contains the URI of the parameter metadata, along with some other metadata files we use.
In most PX4 vehicles the URI of the parameter metadata is a MAVFTP URI, and we have the metadata compressed on the vehicle. Vehicles without much memory instead provide a URL to some server with the file.
We provide translations too, which are always hosted at some URL, in this case github.
The point of all this is that the data is always up to date with the firmware.
The data currently is all static (except translations) because it is saved into firmware, but there are extensions that will allow us to have dynamic updates if we need them. Use cases for that are things like ArduPilot Lua scripts.
The bundling process is covered here: https://docs.px4.io/main/en/advanced/px4_metadata.html
The component metadata thingy is covered here: https://mavlink.io/en/services/component_information.html
PX4 Metadata | PX4 Guide (main)
PX4 User and Developer Guide