Add language support

[Raptor399]

Implements language support as described in #336.

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• queue - adds this PR to the back of the merge queue
• skip-queue - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[Raptor399]

I'm struggling to conquer the Codacy Static Code Analysis results. Part of the problem is that it seems to be using a different set of ESlint settings from what is available in the repo. When I run pnpm lint and pnpm vue-tsc locally, I do not get the same results as what Codacy comes up with.

Also, Codacy's output provides no detail on what exactly in the source is violating the "Unsafe call of an error type typed value" rule. I've tried to cast and narrow the types involved, but all to no avail.

[Raptor399]

I've brought the number of errors in the Codacy Static Code Analysis down to 10. All of which are in parts of the code that I did not touch. It feels like the code in this repo got security checks bolted on at some point in time, but it was never brought up to scratch accordingly. My pull request is the first non-bot pull request that is actually being validated, and therefore it gets all the violations that were embedded in the code already.

My suggestions:

• Make it possible to locally run the exact production checks that Codacy runs, so you don't run into unexpected findings in a pull request. Something like pnpm lint:production.
• Some checks seem overly strict to me. E.g. having to use switch and literal filenames instead of having them in an array constant in fs.readFileSync() in update-simulator-data.js seems over the top for a nightly build utility script, only introducing unnecessary complexity.
• Verify to which files linter checks should apply. Cypress and Vite config files are likely irrelevant.
• I noticed a difference in Codacy's output when using import { i18n } from "@/plugins/i18n"; versus import { i18n } from "../plugins/i18n"; using a relative path. It made "unsafe access" errors disappear. This was unexpected; maybe it indicates an error in Codacy's configuration?

I'll try to bring down the number of errors to 0 as best I can. That being said, these "Generic Object Injection Sink" and "Unsafe call of an error type typed value." errors are particularly nasty and difficult to resolve.