Make custom brigadier aliases override vanilla aliases

[xaanndeer]

Is your feature request related to a problem?

The problem

When registering a command with a name that already exists in vanilla it overrides the vanilla variant without a namespace. However when said command has aliases that also exist in vanilla, those aliases don't override their vanilla variant.

For example:

I'd like to create a teleport command with the name "teleport" and alias "tp". When running "/teleport" my implementations gets executed instead of the vanilla one (as expected). But when I run "/tp" the vanilla implementation gets executed instead of mine.

Describe the solution you'd like.

Aliases for commands that also exist in vanilla should override the vanilla variant without a namespace.

Describe alternatives you've considered.

After looking at how vanilla handles aliases, I tried to manually register them by redirecting them to my command.

        LiteralCommandNode<CommandSourceStack> literalCommandNode = builder.build();
        commands.register(plugin.getPluginMeta(), literalCommandNode, commandDescription, List.of(commandAliases));
        commands.register(plugin.getPluginMeta(), Commands.literal("tp").redirect(literalCommandNode).build(), commandDescription, Collections.emptySet());

However, this doesn't result in the behavior I expected. When using my alias the command is always incomplete or unknown according to the client. Arguments don't get suggested and running it result in an incorrect argument exception. (Known issue: #10827)

Other

No response