DOCS: Re-organize controls section to conform to content model, DOCF-6394

[duckets]

Description

The new re-organized "controls" section of the docs.

Testing status & QA

Built and checked locally.

Overall Product Risks

Docs only, no product risk.

Comments to reviewers

Pages included:

* [Controls](controls.md)
  * [About controls](about-controls.md)
  * [Control hierarchies](control-hierarchies.md)
  * [Control types reference](control-types-reference.md)
  * [Control usages](control-usages.md)
  * [Control paths](control-paths.md)
  * [Control state](control-state.md)
  * [Record control state history](record-control-state-history.md)
  * [Control actuation](control-actuation.md)
  * [Noisy controls](noisy-controls.md)
  * [Synthetic controls](synthetic-controls.md)
  * [Optimizing controls](optimize-controls.md)

[jo-unity]

Suggested change

- The Input System performs additional event filtering to filter out noise, then calls [`InputDevice.MakeCurrent`](../api/UnityEngine.InputSystem.InputDevice.html#UnityEngine_InputSystem_InputDevice_MakeCurrent) if any non-noise values cause the control to change state. If an input event for a Device contains no state change on a Control that is not marked noisy, then the Device will not be made current based on the event. This avoids, for example, a plugged in PS4 controller constantly making itself the current gamepad ([`Gamepad.current`](../api/UnityEngine.InputSystem.Gamepad.html#UnityEngine_InputSystem_Gamepad_current)) due to its sensors constantly feeding data into the system.

- The Input System performs additional event filtering to filter out noise, then calls [`InputDevice.MakeCurrent`](../api/UnityEngine.InputSystem.InputDevice.html#UnityEngine_InputSystem_InputDevice_MakeCurrent) if any non-noise values cause the control to change state. If an input event for a device doesn't contain a state change on a non-noisy control, then the Input System doesn't mark the device as current based on the event. This avoids, for example, a plugged in PS4 controller constantly making itself the current gamepad ([`Gamepad.current`](../api/UnityEngine.InputSystem.Gamepad.html#UnityEngine_InputSystem_Gamepad_current)) due to its sensors constantly feeding data into the system.

There were a lot of negatives here that were making it hard to parse

[jo-unity]

Suggested change

	- When the application loses focus and Devices are [reset](Devices.md#device-resets) as a result, the state of noisy Controls will be preserved as is. This ensures that sensor readinds will remain at their last value rather than being reset to default values.
	- When the application loses focus and devices are [reset](Devices.md#device-resets) as a result, the state of noisy controls are preserved. This ensures that sensor readings remain at their last value rather than being reset to default values.