fix: include plugins in i18n extraction script

[igobranco]

Description

This PR extract more translations to be translated from the exiting source code, when translated those new strings, it will improve localization.

1. Upgrades the frontend-build to the v14.5.0, with the support for additional source folders.
2. Configure the plugins folder to be used as source folder for i18n extraction.

Executing this command before and after this PR, and the prerequisites. You will see an increase of the extracted strings to be translated.

npm run i18n_extract && grep '"id"' temp/babel-plugin-formatjs/Default.messages.json | wc -l

From 1730 before to 2471 after.

Depends on / prerequisites

Any.

1. feat(formatjs): support additional src folders frontend-build#650 has already been merged. ✔️
2. A frontend-build upgrade - this PR also upgrades this package ✔️

Testing instructions

Run

make pull_translations

Manually translate some new extracted strings to be translated, for example for pt_PT locale add the next json lines to the file src/i18n/messages/frontend-app-course-authoring/pt_PT.json:

  "authoring.problemEditor.selectType.title": "Selecionar o tipo de problema",
  "authoring.problemeditor.selecttype.cancelButton.label": "Cancelar",
  "authoring.problemeditor.selecttype.selectButton.label": "Selecionar",

So when editing a "problem", URL: http://apps.local.openedx.io:2001/authoring/course/course-v1:OpenedX+DemoX+DemoCourse/editor/problem/block-v1:OpenedX+DemoX+DemoCourse+type@problem+block@59c24f8a4d5c46af8bfb5fc9cd4bb611

The modal title and action buttons will be translated/localized, view screenshot:

Related to:

• fix: rename messages.ts to messages.js to fix translation extraction #1801
• feat(formatjs): support additional src folders frontend-build#650

[openedx-webhooks]

Thanks for the pull request, @igobranco!

This repository is currently maintained by @openedx/2u-tnl.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.89%. Comparing base (d8eda24) to head (817f651).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff            @@
##           master    #1802    +/-   ##
========================================
  Coverage   93.89%   93.89%            
========================================
  Files        1153     1153            
  Lines       24054    24054            
  Branches     5200     5096   -104     
========================================
  Hits        22585    22585            
- Misses       1392     1401     +9     
+ Partials       77       68     -9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[igobranco]

@OmarIthawi can you review this?

[igobranco]

Rebase on master to fix a git conflict.

[igobranco]

@bradenmacdonald Can you review this PR, so we can improve localization?

[OmarIthawi]

Thanks @igobranco.

Looks good from my side. @brian-smith-tcril @bradenmacdonald would you mind merging this if all is okay? I don't have permissions to do so.

[brian-smith-tcril]

LGTM!