fix: dodge compatibility with BetterThirdPerson

[Farenheith]

Solves #383

MovementInputMixin captures keyboard movement input at its most raw moment, and serves the purpose of accessing its values before any transformation Minecraft or BetterThirdPerson do. It'll always provide a movement vector not even aligned with world coordinates.

The InputUpdateEvent is the second entry point for movement events, which will serve the purpose of capturing movements done by gamepads. An if is made to ignore the event if a keyboard movement input has not been consumed yet. Why? Because BetterThirdPerson captures both moments and manipulates the vector in both of them, we need to do the same in order not to access already transformed inputs.

When the captured vector is consumed, an alignment to the current camera is done so it'll correspond to the direction the player wants. The camera can be defined by BetterThirdPerson, ShoulderSurfing, or the vanilla one, depending on which option the player is using. The alignment is only done during the getLastMoveVector call as it'll be called by the Dodge action once it confirms a dodge must be done, so we avoid doing unneeded calculations at each input, and we give a chance to the camera mods to do their thing with the perspective.

This way, we solve keyboard and gamepad users, and they have a working dodge with BetterThirdPerson.

This approach has also been tested with ShoulderSurfing and Vanilla Camera, and it works equally with every one of them.

I haven't tested it with Controlify, though, as it doesn't support Minecraft 1.16.5 or Forge. I'll revisit the topic once this PR is accepted and the modification is ported to a compatible version. I tested it only with controllable. Also tested with controlify (see #390)

[Farenheith]

@alRex-U this is ready for review! Thank you for the discussion in the issue! It really helped me to find a way to solve the problem.