Implement MiniMessage Velocity translations

[4drian3d]

resolves https://github.com/PaperMC/Velocity/issues/720

[powercasgamer]

Won't this break existing translations from the lang folder?

[4drian3d]

Won't this break existing translations from the lang folder?

Yes, I was also thinking of integrating a migration once https://github.com/PaperMC/Velocity/pull/1111 is merged

[4drian3d]

Won't this break existing translations from the lang folder?

Yes, I was also thinking of integrating a migration once #1111 is merged

Implemented a migration to the new format, this pull request is ready for another review

[electronicboy]

This has my approval, and the prerequisite PR has been pulled, just need to figure out what to do regarding crowdin

[R00tB33rMan]

Only issue I have when testing is that tooltips appear not properly to parse from the messages.properties file properly

[R00tB33rMan]

Managed to fix it with these changes. Thought this'd help speed up the state of this PR (ignore the messages.properties changes, except for the Plugins: one: or https://github.com/GemstoneGG/Velocity-CTD/compare/libdeflate%40%7B1day%7D...libdeflate

[SpaceYoshi]

I just implemented this into my Paper plugin, and noticed that single quotes behave differently using the code in 'VelocityTranslationRegistry' as opposed to using 'TranslationRegistry.create()' directly. Normally, MessageFormat converts double single quotes '' into '. Now, double single quotes are left unchanged, and a single ' gets removed. Not too big of a deal, but I still wanted to share. Can someone verify this? Notable: MessageFormat.toPattern().

Also: ' and '' are used interchangeably in the property files. Nice addition! 👍