vNext Task: Create Controller Action Popouts in Controller Mapping Profile

[StephenHodgson]

Overview

The SDK needs a component to visualise what "InputActions" are being exposed by the InputSystem.
This would enable a user to test their controller mappings are working as expected

Requires

• Move assigning the interactions to a popout window to remove clutter from the controller mapping profile.
• Add images with action assignments for all known controller types.
• Sync the controller actions to all the variants of the same physical controller.
  • This ensure's we don't have to make multiple controller definitions for the same physical controller for each platform.
  • You'll see a single controller input action window which will assign the actions to every platform

An example of what the known controller type popout would look like:

Notes

• Minimal to no controller code changes should be required to make this happen.
• Figure out if there's issues with using controller images.

Acceptance Criteria

• I can configure a generic controller using the detailed interaction mapping window
• I can configure a generic Open VR controller using the detailed interaction mapping window
• I can configure a WMR Motion Controller using its corresponding controller image
• I can configure a HTC Vive Wand Controller using its corresponding controller image
• I can configure an Oculus Touch Controllerusing its corresponding controller image
• I can configure an Xbox One Controller in using its corresponding controller image

Other controllers and their images will be added when their support has been added.