Add handling of localization tokens to parsers

[Dasch0]

Neb now has localization support, and as a result exported fleet files contain localization tokens where they previously contained regular string constants.

This is mostly a problem for fleet file sharing via the discord bot, where the missile descriptions are all tokenized and appear like:

This PR pulls the english localization data from the resources.assets file in the latest version of nebulous, and adds a localizer regex function to attempt to replace all tokens with their english text values when calling parse_any

Currently testing this PR out in a few servers using my fork of hazel

and finally attached profiler runs generating ~40 new fleet images - seems that the localizer isn't taking too long to run compared to the rest of the parsing.
cProfile Results localize.html
cProfile Results parse_any.html

[jaghaimo]

Thanks, @Dasch0. I will update Hazel today.