feature: MiniMessageTranslator

[kezz]

Closes #971

[mishyy]

I think it would be worth including an equivalent of the MessageFormat-based TranslationRegistry for MiniMessage's String-based translations, to maintain consistency in the level of multi-locale and multi-source (ResourceBundles, Files, etc) support.

[kezz]

This PR has been updated with full documentation and named argument support using virtual components. An example of which is provided below:

Component.translatable(
  "my.minimessage.key", 
  NamedTranslationArgument.component("player_name", player.displayName())
);

[kezz]

I think it would be worth including an equivalent of the MessageFormat-based TranslationRegistry for MiniMessage's String-based translations, to maintain consistency in the level of multi-locale and multi-source (ResourceBundles, Files, etc) support.

I'm unsure what you mean by this. It already has "multi-locale and multi-source" support by allowing you to do whatever you want to turn keys to MiniMessage strings.

[kezz]

As pointed out by FabiHBBBT in Discord, it would be incredibly nice to allow for entire tag resolvers to be wrapped in the same system.

Addressed