refactor: Migration of course details to React query

[ChrisChV]

Description

• Migrates the courseDetails part from the Redux Store to React Query.
• Creates a new CourseAuthoringContext
• Update the pages in <CourseAuthoringRoutes> to use the newly created context.
• Migrates some files to Typescript
• Migrates some tests to use src/testUtils.tsx
• Which user roles will this change impact? "Developer".

Supporting information

• Github issue: Switch from Redux to React Query + Context #2540
• Internal ticket: FAL-4288

Testing instructions

• Verify that the test covers the migration.
• Check all the pages in <CourseAuthoringRoutes>, and verify that all are rendered successfully.

Other information

N/A

Best Practices Checklist

We're trying to move away from some deprecated patterns in this codebase. Please
check if your PR meets these recommendations before asking for a review:

• Any new files are using TypeScript (.ts, .tsx).
• Avoid propTypes and defaultProps in any new or modified code.
• Tests should use the helpers in src/testUtils.tsx (specifically initializeMocks)
• Do not add new fields to the Redux state/store. Use React Context to share state among multiple components.
• Use React Query to load data from REST APIs. See any apiHooks.ts in this repo for examples.
• All new i18n messages in messages.ts files have a description for translators to use.
• Avoid using ../ in import paths. To import from parent folders, use @src, e.g. import { initializeMocks } from '@src/testUtils'; instead of from '../../../../testUtils'

[openedx-webhooks]

Thanks for the pull request, @ChrisChV!

This repository is currently maintained by @bradenmacdonald.

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.

[codecov]

Codecov Report

❌ Patch coverage is 99.01961% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 94.89%. Comparing base (f9e09f0) to head (8f0fc17).
⚠️ Report is 8 commits behind head on master.

Files with missing lines	Patch %	Lines
src/data/apiHooks.ts	89.47%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2724      +/-   ##
==========================================
+ Coverage   94.86%   94.89%   +0.03%     
==========================================
  Files        1233     1235       +2     
  Lines       27940    28254     +314     
  Branches     6332     6408      +76     
==========================================
+ Hits        26505    26813     +308     
- Misses       1364     1370       +6     
  Partials       71       71              

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

[ChrisChV]

@bradenmacdonald This is a big one. It's ready for your review. You can review it commit by commit.

[bradenmacdonald]

Wow, thanks! This is awesome. I tested various pages and didn't see any new bugs resulting from this. Nice work!

Please consider the following changes before you merge. But let's merge this ASAP.

[bradenmacdonald]

What is canChangeProviders ? If you know, can you please add a comment like courseId has? I don't know what this is.

[ChrisChV]

I'm not entirely sure either; it's used a lot in pages-and-resources/discussions

[bradenmacdonald]

Ah, it probably means "can change discussion providers", which would be possible only before the course starts. I don't think it makes sense to have that in the CourseAuthoringContext if it's only about discussions. It should really be something that's decided by the backend, not the frontend, and loaded only when needed to display the discussion settings.