Jenkins Builds

Thanks @Parveshdhull! I tested the build with Spanish and Portuguese (Brazil). Although far from good, it's motivating to see us adding back multilingual support! A few notes:

• There are many missing translations, but that's expected.
• Some translations need more context. For example, the translation key all is set to Todos (referring to all notifications in the AC), but it should use Todas because in both languages we refer to notifications in the feminine. This means that we should probably avoid keys that have too little context. A better key in the JSON files would be all_notifications to give the translator (human or LLM) enough context.
  • Definitely something that will require careful manual review and the reason why we should add one language at a time, otherwise it looks quite unprofessional to see obviously wrong translations.
  • Crowdin has support for the ICU syntax, but we should likely avoid any changes to the format of our translations.
• Since we are talking about adding support for Spanish, we should simplify and remove all specialized es_* files in the repo and focus only in one Spanish locale es.
  • Our efforts should focus on adding more languages instead of variations of the same language, at least until we reach our desired goal of translating the most commonly used languages according to our metrics in app stores.
• Our translation linter may help us delete more unused keys, although it does require double-checking because of false positives.

I'm curious to see the quality of results from an LLM pass on the en.json file to es.json. Definitely won't be great, but curious nonetheless :)