Add support for rotation argument handling.

[NonSwag]

Resolves #11395

Introduced a RotationResolver to handle rotation arguments and added related methods to ArgumentTypes, and argument provider classes. This enables resolving and processing rotation data using CommandSourceStack.

The Vector2f in RotationArgument was just a temp solution because I wasn't sure on whether to add a rotation object that clearly combines a yaw and pitch

[NonSwag]

public class TestCommand {
        public static LiteralCommandNode<CommandSourceStack> create() {
            return Commands.literal("teleport")
                .requires (commandSourceStack -> commandSourceStack.getSender() instanceof Player)
                .then(Commands.argument("position", ArgumentTypes.finePosition())
                    .then(Commands.argument("rotation", ArgumentTypes.rotation())
                        .executes (ctx -> {
                            var sender = (Player) ctx.getSource().getSender();
                            var position = ctx.getArgument("position", FinePositionResolver.class).resolve(ctx.getSource());
                            var rotation = ctx.getArgument("rotation", RotationResolver.class).resolve(ctx.getSource());
                            sender.teleportAsync(position.toLocation(sender.getWorld()).setRotation(rotation.y, rotation.x));
                            return Command.SINGLE_SUCCESS;
                        })))
                .build();
        }
    }

[Warriorrrr]

I think a new rotation wrapper class would be good for this, but will want see what others think first.

[lynxplay]

I'd also be in favour of a rotation type, mostly because we can add some utils on there to e.g. convert to a direction vector.
x and y are also just terrible names so, another good reason for a quick interface + package private record impl.

[NonSwag]

... we can add some utils on there to e.g. convert to a direction vector.

My math skills are too... non-existent... to do something like that
as far as I know a vector consists out of 3 components_?_

[lynxplay]

Just ignore for now, we don't need to add utils yet.
Was just an argument for using a proper type instead of reusing joml's Vector2F

[Warriorrrr]

There should be some way to obtain an instance of this if we want it to be useful outside of commands, RotationImpl can be moved into the math package in api and a static method can be added in this class, the same is currently done in Position for example.

[Warriorrrr]

leftover unused import here