Feature request: Internalization support

[MartynasZilinskas]

Summary

Add internationalization (i18n) support to the UI, using react-i18next or a similar library.

Problem or motivation

The project is still in an early stage, so now is a good time to introduce i18n before more UI text and components are added.

Adding i18n support early would make it easier for non-English-speaking communities to use and contribute to the project. Day-to-day development overhead should be negligible, since core developers can continue working in English while other communities can provide translations for their own languages.

Proposed solution

Introduce an internationalization setup for the frontend, preferably using react-i18next or a similar established library.

The implementation should include:

• A default English translation file.
• A structure for adding additional language files.
• A UI language selector so users can choose their preferred language.
• A way for newly added translations to appear in the language selector without requiring excessive manual work.
• Documentation or guidance explaining how contributors can add or update translations.

It would also be useful to explore how to make community translations easy to contribute, for example by keeping translation files simple and well-organized.

Alternatives considered

Not considered

Additional context

N/A

[MrAlders0n]

I will try to implement this in the next release