Check and setup of Weblate localization process

[andrewtavis]

Terms

• [X] I have searched open localization issues
• [X] I agree to follow activist's Code of Conduct

Description

This issue is to do a test of the Weblate localization platform to see if it's fitting for our needs. Steps included in this issue are:

• [x] Settings a baseline localization quota for a language on Weblate
  • 100% reviewed has been selected
• [x] ~Add a machine translation process to Weblate~
  • I signed up to DeepL and we have a free plan going (500,000 characters per month)
• [x] Localizing a few strings in the UI to check the user flow
• [x] Checking the PR flow to see if it's agreeable to maintainers
• [x] Checking the UI with localization partners to see if it can work for them
• [x] Creating some documentation for localization (LOCALIZATION.md)
  • Add this in the Translator Instructions URL in Transifex's settings
  • Add references to this in the readme and contributing guide
• [x] Updating the localization issue template with the needed information
• [x] Apply for the Libre license for Weblate
• [x] Updating the Localization room on Matrix with information on the new process
  • Changing the header and sending info to the channel
• [x] Inviting people to the new localization process

[andrewtavis]

Note that we need to remake the localization project so that we have en-us as the source language such that it's more clear when we have en-gb or another version as an option :)

• [x] Remake Transifex project is thus an added task
• [x] Check to see if we can have localizations backup others
  • Ex: can Brazilian Portuguese backup Portugal Portuguese (and in reverse) with English as a common backup

[andrewtavis]

Note that we can have a per-language fallback locale: https://i18n.nuxtjs.org/locale-fallback/

[andrewtavis]

Note that included in this now is switching activist over to Weblate :)