frontend: editor: additional control mechanisms

[ES-Alexander]

Context

It is often the case that a Cockpit user will have a joystick / game controller and/or keyboard on-hand as part of their control station setup, and it would be valuable to allow using those as part of the configuration process - especially for devices where fine-grained control may otherwise be awkward.

#448 presents some recommended key-bindings to augment the editing process, so this Issue is instead focused on using peripheral inputs as alternatives to standard mouse/on-screen control.

Suggestions

• the go_to_next_view and go_to_previous_view Actions should work in the editor, on whatever joystick buttons they are already configured to
• the toggle_full_screen Action should work when a regular widget is selected
• joysticks/thumb-sticks can be repurposed to match the on-screen move/resize ones
• a D-pad could be used for incremental depth control for regular widgets, and order/container changing for mini widgets
  • this could similarly apply to the arrow-keys on a keyboard
  • holding Shift could switch these control to widget/variant selection