feat: use atlas in make pull_translations

[OmarIthawi]

Changes

• Bump frontend-platform to bring intl-imports.js script
• Move all i18n imports into src/i18n/index.js so intl-imports.js can override it with latest translations
• Add atlas into make pull_translations when OPENEDX_ATLAS_PULL environment variable is set.

Related PRs

• This pull request creates conflicts with feat: upgraded to node v18, added .nvmrc and updated workflows #556, but it's rather easy conflicts to resolve in package.json

References

This pull request is part of the FC-0012 project which is sparked by the Translation Infrastructure update OEP-58.

Join the conversation on Open edX Slack #translations-project-fc-0012.

Check the links above for full information about the overall project.

Internalization is being rearchitected in Open edX Python, XBlock, Micro-frontend, and other projects. There are a number of immediately visible changes:

• Remove source and language translations from the repositories, hence no .json, .po or .mo files will be committed into the repos.
• Add standardized make extract_translations in all repositories
• Push user-facing messages strings into openedx/openedx-translations.
• Integrate root repositories with openedx/openedx-atlas to pull translations on build/deploy time

Breaking Changes

One of the primary goals of the project is to avoid breaking changes. If you noticed any suspicious code, please raise your concern. But before that, please know the strategy we're following to avoid breaking changes

For Micro-frontends and their template:

• Legacy hardcoded translations are kept into the repo.
• Consolidate all i18n imports into src/i18n/index.js
• Add atlas integration in make pull_translations but only if OPENEDX_ATLAS_PULL is set
• Bump frontend-platform and use intl-imports.js to generate up to date import files

[openedx-webhooks]

Thanks for the pull request, @OmarIthawi! 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.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (a834c30) 0.00% compared to head (772fcc8) 0.00%.

❗ Current head 772fcc8 differs from pull request most recent head c837dcd. Consider uploading reports for the commit c837dcd to get more accurate results

Additional details and impacted files

@@          Coverage Diff           @@
##           master    #576   +/-   ##
======================================
  Coverage    0.00%   0.00%           
======================================
  Files           2       2           
  Lines           7       7           
======================================
  Misses          7       7           

Impacted Files	Coverage Δ
src/index.jsx	0.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[brian-smith-tcril]

Perfect! LGTM!

tested locally by using the Zeit-Labs:atlas template to create a new repo

nvm use
npm install
npm start

worked as expected!

[openedx-webhooks]

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