Allow interpreting JoyAxis as JoyButton

[Sauermann]

Let the user configure, if a JoyAxis should be interpreted as a pair of JoyButtons (negative and positive side).

When an axis is configured as a button, then InputEventJoypadButton-events are sent instead of InputEventJoypadMotion-events for this axis.

resolve #72636

Being unfamiliar with this part of the code-base, It is likely, that I have missed some details.

MRP for testing: AxisButton.zip

[KoBeWi]

Why not HashMap<int, LocalVector> ?
EDIT:
Actually LocalVector might be faster, idk.

[Sauermann]

I was under the impression, that LocalVector was more appropriate than HashMap, because I can access the content by integer indices, so there is no need for creating the hash values.

[KoBeWi]

I left some comments, but looks fine overall.

[RandomShaper]

If there's the problem that is_action_pressed/released() doesn't have enough resolution (e.g., two quick presses in a row are registered as a continuous press, with no release in the middle), #77062 could help. That one would only address the problem on Android, and for other OS abstrations that are rearchitected to split main and OS threads.

It'd be interesting to know if on non-Android platforms, there's an issues at the moment with is_action_pressed/released() and that's forcing games to need a feature like the one implemented here.

[Sauermann]

As discussed in a previous PR-review meeting, there are better ways to resolve the linked issue. Closing.