feat: Migrate pages and resources to React Query

[ChrisChV]

Description

• Migrates the pages and resources from React Redux to React Query
• Stops using the courseApps and XpertSettings models.
• Updates some Settings Modals of course Apps: Learning Assistant, Live, Ora, Proctoring, Progress, Teams, Wiki, Xpert.
• Which user roles will this change impact? "Developer".

Supporting information

• GitHub Issue: Switch from Redux to React Query + Context #2540
• Internal ticket: https://tasks.opencraft.com/browse/FAL-4288

Testing instructions

• Create a new course for testing.
• Go to Content > Pages & Resources
• Verify that the list of apps is rendered as expected.

Learning Assistant

• Install the learning assistant plugin.
• Add LEARNING_ASSISTANT_AVAILABLE = True to your cms/envs/private.py
• Restart your instances
• Go to the Pages and resources page and verify that you can see the Learning Assistant card.
• Verify that you can open the settings modal.
• Verify that you can enable and disable the app.

Live

• Go to the Pages and resources page.
• Verify that you can see the Progress card.
• You can try disabling the app, but there is a known issue in this app: Course Live Feature Not Working (Release: Teak) #2922

ORA

• Create an ORA xblock in your course.
• Go to the Pages and resources page and verify that you can see the Flexible Peer Grading for ORAs card.
• Verify that you can open the settings modal.
• Verify that you can enable and disable the app.

Proctoring

• Add ENABLE_PROCTORED_EXAMS = True to your cms/envs/private.py
• Go to the Pages and resources page and verify that you can see the Proctoring card.
• Verify that you can open the settings modal.
• Verify that you can enable and disable the app.
• Test updating the extra settings.

Progress

• Go to the Pages and resources page.
• Verify that you can see the Progress card.
• Verify that you can enable and disable the app.
• Test updating the extra settings.

Teams

• Create the waffle flag teams.enable_teams_app activated for Everyone.
• Go to the Pages and resources page and verify that you can see the Teams card.
• Verify that you can enable and disable the app.
• Test updating the extra settings

Wiki

• Go to the Pages and resources page.
• Verify that you can see the Wiki card.
• Verify that you can enable and disable the app.
• Test updating the extra settings.

Xpert

• Create the waffle flag summaryhook.summaryhook_summaries_configuration activated for Everyone.
• Go to the Pages and resources and verify that you can see the Xpert unit summaries card.
• Verify that you can enable and disable the app.
• Test updating the extra settings.

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 96.61017% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 96.02%. Comparing base (f5041a7) to head (41ade6a).
⚠️ Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
...-resources/app-settings-modal/AppSettingsModal.tsx	91.30%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3222      +/-   ##
==========================================
+ Coverage   95.93%   96.02%   +0.09%     
==========================================
  Files        1397     1393       -4     
  Lines       33622    33589      -33     
  Branches     7701     7711      +10     
==========================================
- Hits        32256    32255       -1     
+ Misses       1323     1291      -32     
  Partials       43       43              

☔ View full report in Codecov by Harness.
📢 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.