i18n: update coverage to auto-detect browser languages

[Jaehyuk-Lee]

f285d76: coverage.ts detects language from the web browser.
c0cf1de: fix Korean translation
8cbefb1: remove languagesArr parameter from browserLanguagesToLang function.

Removing languagesArr parameter

Current Situation

The browserLanguagesToLang function has a comment saying it only takes navigator.languages as input. But it still receives this value as a parameter, which is unnecessary.

Option 1: Remove the parameter

If the function only handles navigator.languages, we can remove the parameter and use navigator.languages directly inside the function.

Option 2: Generalize the function

If we want to support other locale arrays beyond navigator.languages, we could keep the parameter and rename the function to localesToLang. This makes it clear that the function converts any locale array to a cactbot language.

---

This PR implements Option 1. Let me know if Option 2 is preferred.

[Jaehyuk-Lee]

By the way, this should not be deleted.

ACT web browser

Because you cannot change the language setting of the ACT web browser (I would call this way).

[valarnin]

I think that option 2 is better from a logic standpoint, with a wrapper for pulling from browser navigator.languages, for CLI and testing purposes, e.g.:

export const localesToLang = (locales: readonly string[]): Lang => {
// ...
};

export const browserLanguagesToLang = (): Lang => localesToLang(navigator.languages);

But this is pretty subjective.

[Jaehyuk-Lee]

@valarnin

I think that option 2 is better from a logic standpoint, with a wrapper for pulling from browser navigator.languages, for CLI and testing purposes

That's a fair point. I hard-coded 'ko' when I tested oopsy on #947.

[valarnin]

Because you cannot change the language setting of the ACT web browser

Can you file an issue on the OverlayPlugin repo for this and I'll see about tackling it towards the end of the expansion, if it's even possible?