🔧 Use Node.js 22 and bump i18next-cli

[LitoMore]

Changes

• Use Node.js 22 for GitHub Actions
• Migrate i18next-parser to i18next-cli

The legacy i18next-parser package blocked us from upgrading the Node.js version because it does not support Node.js 22 or later. The i18next team has deprecated the i18next-parser and recommends users migrate to i18next-cli. I migrated it to i18next-cli manually and made some cleanup (comments, configuration) using AI (Opus 4.6).

Those translation files have been changed because the i18next-cli supports sorting keys. I just used its default configurations. Sorting keys can make the content in translation files consistent, so I kept it. Please let me know if you have any thoughts.

[Schneegans]

Thanks for looking into this. However, missing translations are now inserted as "" in the translation files which makes them disappear in the GUI. Is it possible to fallback to the English strings again?

Also, it's not very nice that we now have to list the locales in the i18next.config.ts. This way, whenever someone adds a new language on weblate, we need to update this list manually. Is there some way around this?