feat: add controller input extensions

[wlsnmrk]

(Edited to more accurately describe the PR after a substantial rework; see comment below.)

This PR adds extension methods to simulate controller button and analog-axis input by firing InputEventJoypadButton and InputEventJoypadMotion. This behavior is analogous to existing behavior for keyboard- and mouse-input simulation.

Simulation of controller input by way of mapped actions is left to the existing action-input simulation code.

This PR also:

• Provides a workaround, for actions in general, for a possible Godot bug (which has been reported and a fix submitted). The workaround ensures that input strength values are clamped between 0 and 1.
• Renames the existing *ControlExtensions classes to *InputExtensions (for improved clarity and to avoid ControllerControlExtensions).
• Bumps the test Godot project to v4.2 and adds a setting to name new scene files using PascalCase (as all existing scenes are).
• Updates editorconfig to use LF as the default line ending (easing development on Windows). Some file types (e.g., .bat, .cmd) may override this setting.
• Adds tests for the new controller-input extensions.
• Updates the README to describe the new controller-input extensions.

---

The new controller-input methods are extensions on Node (as are the keyboard-input extensions) and are:

• void PressJoypadButton
• void ReleaseJoypadButton
• void TapJoypadButton
• async Task HoldJoypadButtonFor
• void MoveJoypadAxisTo
• void ReleaseJoypadAxis
• async Task HoldJoypadAxisFor

The "Joypad" naming convention mirrors the names of the associated Godot events.

---

BREAKING: Classes containing input extension methods have been renamed, so any code that calls them directly (e.g., ActionsControlExtensions.StartAction(myNode, "my_action") instead of the more idiomatic myNode.StartAction("my_action")) will break with this change.

[jolexxa]

This looks good to me 😄

[wlsnmrk]

Reworked to provide controller-input event simulation. Action-based controller input simulation (for use with Input.GetActionStrength(), Input.GetAxis(), and Input.GetVector()) can still be accomplished with the existing action-input extensions. Convenience methods to provide controller semantics for action inputs, as originally proposed, could be added later if necessary.

Also squashed most commits to make the git history more readable.

[jolexxa]

Thank you so much for doing this 🙌