feat: optionally collect JS translations on deploy

[mtyaka]

If the EDXAPP_COMPILE_JSI18N is enabled, this will invoke the compilejsi18n management command when deploying edxapp.

This is useful when you use custom JS translations for example via a theme.

Test instructions:

I set up a sandbox using code from #6679 to automatically install some custom JS translations. These are the relevant ansible vars:

EDXAPP_DEFAULT_SITE_THEME: simple-theme
SIMPLETHEME_ENABLE_DEPLOY: true
EDXAPP_COMPILE_JSI18N: true
EDXAPP_PREPEND_LOCALE_PATHS:
  - "{{ EDXAPP_COMPREHENSIVE_THEME_DIRS[0] }}/simple-theme/i18n/conf/locale"
SIMPLETHEME_I18N_DJANGO:
  - lang: ar
    domain: djangojs
    messages: |
      msgid "Submit"
      msgstr "تقديم YYY"
      msgid "Add a Post"
      msgstr "إضافة منشور ZZZ"

1. Create an account and log into the sandbox.
2. Enroll into the Demo course.
3. Go to https://mtyaka.opencraft.hosting/update_lang/ and switch the language to Arabic (ar).
4. Go to the forum, click the button to create a new post, and verify that the submit button at the bottom contains the custom translation "تقديم YYY" and that one of the headings on the page says "إضافة منشور ZZZ".
5. If you have SSH access to the sandbox (213.32.74.79), go to the /edx/app/edxapp/edx-platform folder and run git status. You should see some modified files under lms/static/js/i18n (the files were modified because the compilejsi18n management comment modifies them after collecting JS translations from LOCALE_PATHS).

Sandbox:

• https://mtyaka.opencraft.hosting/

Configuration Pull Request

Make sure that the following steps are done before merging:

• A SRE team member has approved the PR if it is code shared across multiple services and you don't own all of the services.
• Are you adding any new default values that need to be overridden when this change goes live? If so:
  • Update the appropriate internal repo (be sure to update for all our environments)
  • If you are updating a secure value rather than an internal one, file a SRE ticket with details.
  • Add an entry to the CHANGELOG.
• If you are making a complicated change, have you performed the proper testing specified on the Ops Ansible Testing Checklist? Adding a new variable does not require the full list (although testing on a sandbox is a great idea to ensure it links with your downstream code changes).
• Think about how this change will affect Open edX operators. Have you updated the wiki page for the next Open edX release?

[openedx-webhooks]

Thanks for the pull request, @mtyaka! I've created OSPR-6553 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[natabene]

@mtyaka Thank you for your contribution. Please let me know once it is ready for our review.

[farhaanbukhsh]

👍

• ✅ I tested this: on the sandbox and saw the configuration
• ✅ I read through the code
• ❌ I checked for accessibility issues
• ❌ Includes documentation
• ❌ I made sure any change in configuration variables is reflected in the corresponding client's configuration-secure repository.

[mtyaka]

@natabene This is ready for review.

[nadeemshahzad]

@mtyaka Can you please rebase the PR? thanks

[mtyaka]

@nadeemshahzad Thanks for looking at this. I rebased it and resolved the conflicts.

[openedx-webhooks]

@mtyaka 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.