chore: Convert lang/en.lyaml to native JS objects

[joe-yeager]

Description and Context

Does not delete the en.lyaml file or modify the i18n functionality at all. This PR is purely additive so we can begin the conversion.

[camden11]

Is there any advantage to adding this without making the changes to actually pull data from it? Won't it just get out of date when we make copy updates?

[joe-yeager]

Is there any advantage to adding this without making the changes to actually pull data from it? Won't it just get out of date when we make copy updates?

@camden11 - good question, I was thinking when we made copy changes we could update the new file, delete the lines from the old file, and switch to use the new strings. I'm going to work on getting all of the i18n calls ported over when I get some more time

[camden11]

That makes sense to me. I guess I don't feel super strongly, but I could see it making sense to include a version of the i18n function that works with the JSON file with this PR so we can get started with that right away

[joe-yeager]

That makes sense to me. I guess I don't feel super strongly, but I could see it making sense to include a version of the i18n function that works with the JSON file with this PR so we can get started with that right away

@camden11 In the new version we wouldn't need the i18n function. This is a js file and the functions can be directly invoked

[camden11]

Ohhhhh 🤦 . I had it in my head that this was JSON like LDL even though you had native JS in the title and everything haha.