Prevent parent addon localization from replacing library strings

[aleksandr-kotlyar]

Summary

• replace the eight non-enUS localization substitution markers with the current exported LibMagicUtil tables
• preserve existing translations and English fallback values
• keep embedded copies independent from the parent addon localization project

Why

Some addon packaging paths process localization markers inside embedded externals with the parent addon project ID. That injects unrelated strings into LibMagicUtil locale files. Parent projects with multiline keys can then produce invalid Lua and stop loading, as seen in BulkMail2Inbox.

Committing the generated LibMagicUtil locale snapshots removes the ambiguous packaging step while retaining the library translations.

Validation

• Lua 5.1 syntax check passes for every locale file
• all eight locale files contain the 22 LibMagicUtil keys
• no localization marker or BulkMail string remains in the affected files

Related

• BulkMail PR #48 pins this commit for package reproducibility.