feature(api, minimessage): Replace TranslationRegistry with a generic TranslationStore

[kezz]

This PR deprecates for removal the entire TranslationRegistry system in favour of a more generic TranslationStore system.

Having a generic system allows us to easily implement a TranslationStore for Component or MiniMessage translation (which this PR does).

Additionally, an abstract implementation of TranslationStore is provided for those who may wish to make their own custom type of TranslationStore. For example, one could easily create a JSONTranslationStore that provides component-based translations reading from a list of JSON strings.

For those scared about the big deprecation, it's a simple one line change for your codebase, no other API surface has been changed. Additionally, the old system continues to work identically to the new one.

- final TranslationRegistry myRegistry = TranslationRegistry.create(myKey);
+ final TranslationStore.StringBased<MessageFormat> myRegistry = TranslationStore.messageFormat(myKey);

Closes #1184