LF-4349 Finish crowdin setup to support the addition of new languages

[kathyavini]

Description

As just discussed a few minutes ago 🙂

• Add the {{ matrix.locales }} to each PR title to disambiguate them
• Make upload translations and auto-approve uploaded GitHub variables dispatch inputs (with fallback to false) so they can be changed without having to merge new versions of these files

Testing plan:

• variables have been set on the repository level
• this is opened against integration; once merged I will test toggling the environmental variables and running the upload to make sure it behaves as expected
• if successful I will open a new PR to merge to main

Jira link: https://lite-farm.atlassian.net/browse/LF-4349

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Passes test case
• UI components visually reviewed on desktop view
• UI components visually reviewed on mobile view
• Other (please explain)

Can't test; actions workflow 🙁

Checklist:

• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The precommit and linting ran successfully
• I have added or updated language tags for text that's part of the UI
• I have added "MISSING" for all new language tags to languages I don't speak
• I have added the GNU General Public License to all new files

[Duncan-Brain]

Question: should we also remove the auto trigger for integration branch upload?

[kathyavini]

@Duncan-Brain I'm totally happy to remove the auto-trigger! It sounds like we won't return to integration-based development for a long time and the manual dispatch has been fine.

[Duncan-Brain]

We will want a PR to add these changes on main too right for it to work there? (I assume thats what the workflow inputs thing meant)

[kathyavini]

We will want a PR to add these changes on main too right for it to work there? (I assume thats what the workflow inputs thing meant)

Yup, I was thinking to clear the CrowdIn sources and do more testing while it's on integration, and if checks out, open PR against main (just to keep down the number of commits added to main) in case something is not right yet.