Crowdin integration for real-time syncing of translation files

[churik]

Problem

We need a centralized and collaborative system for managing translations. Currently, all translations are handled manually in the repository, making updates slow and error-prone. Crowdin has been selected as the preferred tool for managing and scaling multi-language support.

Implementation

• Set up Crowdin project and link it to the GitHub repository.
• Configure target languages and upload current source files (en.json).
• Map existing translation files to Crowdin structure.

Acceptance Criteria

• Crowdin project is initialized and connected to the GitHub repo
• Source (en.json) and all existing locale files are uploaded
• Translation files can be edited in Crowdin interface

Notes

• This step lays the foundation for future automation and contributor access.
• Include key contributors (e.g. Docs team) in the Crowdin project.

Future Steps

• Document contributor workflow
• Set up CI sync to and from Crowdin

[ilmotta]

Linking to my comment in another internationalization issue: #22607 (comment). Essentially, I think the implementation and acceptance criteria need some work and that a collaborator should first experiment with Crowdin to understand in detail how it works, limitations, and so on. Armed with this knowledge, they should help refine the acceptance criteria and issues in the the internationalization epic.

To give an example:

Source (en.json) and all existing locale files are uploaded

Uploaded where? How is Crowdin going to manage sources from different status-mobile environments? Before attempting to answer this and other questions, a collaborator will need to dive deeper.