refactor: change to useIntl

[KristinAoki]

Description

This PR replaces injectIntl and intlShape with useIntl. injectIntl and intlShape are both deprecated. It should be noted that this PR skips the refactor in the following places:

• progress-tab folder
• Section.jsx
• SequenceLink.jsx

Each of these has an open PR that includes the refactor (#1619, #1632)

[openedx-webhooks]

Thanks for the pull request, @KristinAoki!

This repository is currently maintained by @openedx/committers-frontend-app-learning.

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.

Details

---

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.

[KristinAoki]

@openedx/committers-frontend-app-learning this PR is ready to be reviewed

[codecov]

Codecov Report

Attention: Patch coverage is 95.80420% with 6 lines in your changes missing coverage. Please review.

Project coverage is 90.18%. Comparing base (af432ea) to head (391096b).
Report is 2 commits behind head on master.

Files with missing lines	Patch %	Lines
.../access-expiration-alert/AccessExpirationAlert.jsx	0.00%	2 Missing ⚠️
src/alerts/enrollment-alert/EnrollmentAlert.jsx	0.00%	2 Missing ⚠️
...rc/alerts/logistration-alert/LogistrationAlert.jsx	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1634      +/-   ##
==========================================
- Coverage   90.18%   90.18%   -0.01%     
==========================================
  Files         339      338       -1     
  Lines        5810     5726      -84     
  Branches     1409     1379      -30     
==========================================
- Hits         5240     5164      -76     
+ Misses        552      543       -9     
- Partials       18       19       +1     

☔ 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.

[bradenmacdonald]

Wow, thanks for doing this! I'm so happy to see it cleaned up :)

I wasn't sure how to test some of the things, e.g. the Calculator component that you changed from a class component to a function component. But the code looks good to me and the things I did test were working the same.

[bradenmacdonald]

Nit/optional: this function isn't really needed at all - can just use setEquation(event.target.value) directly.

[bradenmacdonald]

@KristinAoki Would you be able to merge this soon ? Or would you like me to? I'm worried we'll start to get more conflicts if we wait longer.

[jristau1984]

@bradenmacdonald if you are able to take this over, please do. Thanks.

[bradenmacdonald]

Rebased, and I figured out how to test the calculator - seems to be working fine. Gonna merge now.