add NamespacedKey resolver

[Grabsky]

this PR adds value resolver for org.bukkit.NamespacedKey with resource_location brigadier type to support nice client-side formatting

bumped Lamp version to 3.0.4-SNAPSHOT

[Grabsky]

added missing final keywords to parameters

[Revxrsal]

This PR looks good to me, though I wonder if it would be better to merge that, or add a way to register your own Brigadier arguments and then you can add as many fancy brigadier stuff as you want?

[Grabsky]

Yes, that'd be much better and more flexible. I thought about that already and by taking inspiration from cloud, I think there could be something like BrigadierManager which instance could be accessed from BukkitCommandHandler.

final BrigadierManager brigadier = BukkitCommandHandler#getBrigadierManager();

And I think there should be two methods in that class:

// Class<?>, ArgumentType<?>  -  for instances of brigadier's ArgumentType
brigadier.bind(NamespacedKey.class, ResourceLocationArgument.id());
// Class<?>, String  -  for 'minecraft:' keys specifically; using MinecraftArgumentType.getByKey(String)
brigadier.bind(NamespacedKey.class, "resource_location"));

Second method could technically fallback to the first once it gets non-null ArgumentType<?> from Minecraft internals.

BrigadierManager class could later provide more brigadier-exclusive API (supposing it has more features, not entirely sure if there is anything worth noting).

Naming is just an example; let me know what you think about such structure.

[Revxrsal]

Brigadier API has been implemented. You can freely implement this feature yourself