Replace json-styled translations with string-value translations

[HenryLoenwind]

Replaced the json-styled translations that were used by the configuration screen with pure text (vanilla format) versions.

Adapted the configuration screen to apply the formatting in code.

A number of keys had to be split for this to work.

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

[sciwhiz12]

To add context, after discussion in Discord prompted by me, we decided that it would be best for NeoForge's language files to only use string-values in its translations.

This is primarily because Crowdin does not understand the extended syntax that some translation keys currently use, leading to problems such as Crowdin mistakenly allowing translators to translate the color field of components in the extended syntax.

Mods are free to use the extended syntax (as it stands now or whatever it may be in the future) based on their own design decisions on how they will handle translations, but as far as NeoForge itself is concerned, our use of Crowdin necessarily locks us into using string values. (Unless we find a way to get Crowdin to understand the extended syntax, but that's unlikely in my opinion.)

[sciwhiz12]

Other than my remaining suggested change, the PR looks fine to me. Once it's done, I'll merge it in short order.

[qznfbnj]

Is this intended?

[sciwhiz12]

Is this intended? -- snipped image --

@qznfbnj, what are you referring to?

[qznfbnj]

Is this intended? -- snipped image --

@qznfbnj, what are you referring to?

[sciwhiz12]

Ah, that makes it more clear. @HenryLoenwind, could you please fix that minor issue as well?

[neoforged-releases]

🚀 This PR has been released as NeoForge version 21.1.36.