chore(i18n): add eloqnt lint to catch translation errors

[amannn]

Description

Hey! I maintain eloqnt/cli, a linter for translation files, and have been running it against public repos to see whether their catalogs carry errors.

For Folo it found 48 errors:

• unreachable-plural-case: 45
• inconsistent-args: 3

For example, the Japanese and Chinese translations of settings.invitation.earlyAccess carry a <strong> tag that the English source doesn't have:

Folo/locales/settings/en.json

Line 552 in fac0b08

"invitation.earlyAccess": "Folo is currently requires an invitation code to use.",

Folo/locales/settings/zh-CN.json

Line 552 in fac0b08

"invitation.earlyAccess": "Folo 目前处于<strong>早期开发</strong>状态，需要邀请码才能使用。",

The three strings with inconsistent-args also still described Folo as being in early access, which the English no longer says, so they were regenerated with eloqnt translate. I also corrected a typo in the English source of that message ("Folo is currently requires").

The other 45 are _one translations in ja, zh-CN and zh-TW, which i18next can never select because those locales only have an other plural form.

Up to you if you're interested in adopting eloqnt/cli, but you might want the translation fixes in this PR to clean up your translation files.

PR Type

• Feature
• Bugfix
• Hotfix
• Other (please describe): tooling + translation file fixes

Screenshots (if UI change)

Demo Video (if new feature)

Linked Issues

Additional context

Changelog

• I have updated the changelog/next.md with my changes.

[DIYgod]

Thanks for running the linter on Folo and for the fixes! We'd like to take the translation changes (the unreachable _one plural forms and the stale invitation strings), but we'd rather not add a new tool to our lint script or take the lockfile churn. Could you drop the chore(i18n): add eloqnt lint commit so this PR only contains the locale fixes? Then we can merge it.

[amannn]

@DIYgod Sure thing, the PR is now up to date containing only the translation fixes!