Deprecate react-test-utils other utils 1/2

[diana-villalvazo-wgu]

Description

On previous effort was missing deprecation of formatMessage, useKeyedState and mockUseKeyedState
So it was addressed on this PR.

• For formatMessage we removed it and just use the real defaultMessage to compare on tests.
• Was replaced useKeyedState by useState and in the related tests mockUseKeyedState was removed and replaced by a jest spy for native react useState.

Support Information

Closes #376

[openedx-webhooks]

Thanks for the pull request, @diana-villalvazo-wgu!

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

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 90.18%. Comparing base (16a6ccd) to head (2bef2bb).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #378      +/-   ##
==========================================
- Coverage   90.20%   90.18%   -0.03%     
==========================================
  Files         143      143              
  Lines        2206     2200       -6     
  Branches      476      452      -24     
==========================================
- Hits         1990     1984       -6     
- Misses        204      208       +4     
+ Partials       12        8       -4     

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

[brian-smith-tcril]

Overall this looks great!

I left a couple comments, looking forward to hearing your thoughts!

[brian-smith-tcril]

This is super close to ready to land!

I left a few more comments in places where it'd be good to add comments with context similar to the ones in FileRenderer/hooks.test.js. Once those are in this should be good to go!

[brian-smith-tcril]

Perfect!

Thanks for working through my questions with me!