joystick: indicate expected motion axes for axis names

[ES-Alexander]

Current behaviour

Axis inputs can be assigned to Manual Control axes, which have single-letter names and behaviour that's dependent on the firmware of the vehicle's autopilot.

This is causing confusion for users, and makes joystick configuration less intuitive than it could be.

Expected or desired behaviour

Check the vehicle firmware, and display axis labels (e.g. Axis X (forward)) that are conditional on how it is known to implement manual control axis handling.

Firmware	X	Y	Z	R	S	T
ArduSub	Forward (/Pitch1)	Lateral (/Roll1)	Vertical	Yaw	Roll	Pitch
ArduRover	-	Steer	Throttle	-	-	-
ArduCopter	Pitch	Roll	Throttle	Yaw	-	-
ArduPlane	Pitch	Roll	Throttle	Rudder	-	-
PX4	Pitch	Roll	Throttle	Yaw	-	-

Prerequisites

• I have checked to make sure that a similar request has not already been filed or fixed.

Footnotes

1. when using the roll/pitch toggle - we can leave this out of the first pass ↩ ↩²

[ES-Alexander]

Vaguely related to #2060.

[ES-Alexander]

Building on #2476 and ideas from #2479, this could to some extent be implemented using data-lake aliases/renames. If we allow multiple aliases per variable then that may not work, but if we create effectively a 1:0/1 mapping of data-lake IDs to nicknames then the nickname could override the original name wherever it's displayed (with a restore option in the data-lake table), so the setup code for a given vehicle type could set aliases for the joystick input axis variables, which then shows up in the joysticks interface.