Initial localization support

[NebelNidas]

Inspired by Enigma's and JADX's equivalents, but heavily stripped down. Only supports mapping format names for now, exception messages are going to be tackled in a separate PR.

[modmuss50]

I dont think we should localise error messages like this
It makes it harder to search for solutions, harder for people trying to provide support, and doesn't really benefit users. We dont localise error messages in other projects, especially none user facing ones like this.

[sfPlayer1]

We could maybe introduce error codes that make it accessible for replacement on the embedding application side?

[NebelNidas]

That's the goal, having a central ErrorMessages class holding all the error messages MIO uses in the form of Translatables. Consumers can either translate the Translatable to a given locale, or manually check for equality with a given error message.

But as mentioned above, that's going to be a separate PR (probably after #94 is merged)

[modmuss50]

Most of this shouldnt even be translated, other than maybe "File". Im not really sure this should be handled in mapping-io.

[NebelNidas]

Some languages will need to hyphenate individual words, switch their order around, or even outright translate the format names. For example in German, you'd have Tiny-v2-Datei and IntelliJ-Migrationszuordnungsdatei (at least when going with the German language pack's translation).

I think this makes sense being part of Mapping-IO natively, as I don't want to duplicate the translation files across a dozen different applications like Enigma, Matcher and JADX, just to name a few. And you're not forced to use MIO's translations either, you can always delegate to a custom localization system via Translatable#translationKey(). Not to mention that these facilities are required for #88 and #94 to provide user-friendly warnings and error messages e.g. in Enigma.