feat: Connect bulk migration backend with frontend [FC-0097]

[ChrisChV]

Description

• Connects the Confirm button with the bulk migrate backend
• Updates the library page to get the migration task status and refresh the component on success.
• Which user roles will this change impact? "Course Author".

Supporting information

• Github issue: Migrate Legacy Libraries Flow #2201
• Depends on: feat: bulk modulestore migration [FC-0097] edx-platform#37381
• Internal ticket: FAL-4253

Testing instructions

• Use this branch of edx-platform: feat: bulk modulestore migration [FC-0097] edx-platform#37381
• Run make migrate in the cms shell.
• Create some legacy libraries.
• Create some components in the legacy libraries.
• Go to the legacy libraries list page and click on Review Legacy Libraries button.
• Select multiple legacy libraries.
• Select one V2 library.
• Click on Confirm
• Wait for the success message and check that the component list is refreshed. Verify that you can see the new collections with the components from the legacy libraries.

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).
• Deprecated propTypes, defaultProps, and injectIntl patterns are not used 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.
• Imports avoid using ../. 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.

---

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 98.79518% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 94.72%. Comparing base (1d6fdc3) to head (d6638bd).

Files with missing lines	Patch %	Lines
src/legacy-libraries-migration/data/api.mocks.ts	92.30%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2493      +/-   ##
==========================================
+ Coverage   94.71%   94.72%   +0.01%     
==========================================
  Files        1202     1205       +3     
  Lines       26845    26921      +76     
  Branches     6023     5883     -140     
==========================================
+ Hits        25425    25500      +75     
- Misses       1350     1362      +12     
+ Partials       70       59      -11     

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

[rpenido]

LGTM 👍
Thank you for your work, @ChrisChV!

• I tested this using the instructions from the PR
• I read through the code
• I checked for accessibility issues
• Includes documentation

[ChrisChV]

FYI: Waiting for a question about the repeat strategy: #2201 (comment)