Reintroduce and Automate Multi-Language Support

[churik]

Feature Issue

User Story

As a multilingual user or contributor, I want the Status app to support multiple languages so that I can use and contribute to the app in my native language, improving accessibility and usability globally.

As a developer, I want to integrate Crowdin with our translation workflow so that new and updated translations can be continuously delivered and crowd-sourced in a decentralized, privacy-aligned manner.

---

Description

Summary:
We are reintroducing multi-language support in the Status mobile app. This feature previously existed and dynamically loaded translation files from translations/ based on the device's locale settings (if not English). Due to significant user demand and the team's alignment during offsite discussions, this functionality will be restored and enhanced with better infrastructure and processes.

Key improvements:

• Try to use Crowdin for collaborative and AI-assisted translation management.
• Enable community-driven translation contributions in alignment with Status's open-source, decentralized ethos.
• Introduce CI-based automation to sync translation files between Crowdin and the GitHub repo.
• Ensure fallback to English where translations are incomplete or unavailable.
• Provide tooling/guidance for developers to easily mark new strings and submit them to Crowdin.

Use Cases:

• New and existing users across non-English-speaking regions.
• Contributors who wish to translate or refine app strings via Crowdin.
• QA testers validating localized flows in major languages (ES, FR, PT, ZH, RU, etc.).
• Developers needing visibility into untranslated or missing keys.

---

Acceptance Criteria

By the end of this epic, the Status mobile app should support locale-based language loading using the existing translations/ directory, with a fallback to English when localized strings are missing. Integration with Crowdin must be established, enabling real-time syncing of translation files between the GitHub repository and the Crowdin platform.

The contribution workflow should be clearly documented, allowing both internal team members and the community to easily submit or improve translations through Crowdin. Updates from Crowdin should be automatically synchronized via CI (e.g., GitHub Actions), minimizing manual effort and keeping translations up-to-date.

Developers should have tools or processes in place to identify untranslated or newly added keys (e.g., using extraction scripts), and QA should validate that translations do not visually break the UI, especially in critical flows and across key languages.

---

Notes

• Docs team recommends Crowdin as the platform of choice. It supports AI-assisted and community-managed translations.
• Crowdin provides official GitHub Action integration: https://github.com/marketplace/actions/crowdin-action
• Follow privacy-first principles: ensure no telemetry or identity data is leaked through translation tooling.
• Languages to prioritize (based on current userbase and historical demand): start from Spanish and proceed based on user data from stores

[ilmotta]

@churik @shivekkhurana related to internationalization, we will also need to cater for number and date formatting. I have the impression the code is not ready yet to handle numbers and dates in some places. For example, the function utils.number/small-number-threshold returns a value like <0.001, hardcoding the period, which is the incorrect separator in many languages.

I think this can be a separate issue because the changes will be different than normal language translations.