feat: Add new fields in modulestore migratior serializers [FC-0112]

[ChrisChV]

Description

• target_collection and task_uuid added to migration serializers
• migration_summary added to Migrations. Add logic in the migration to build the summary.
• unsupported_reasons added to Migrations. Add logic in the migration to save this reasons.
• Which edX user roles will this change impact? "Course Author", "Developer".

Supporting information

• Github issue: Import Details Page frontend-app-authoring#2526
• Used in: feat: Import Course Details Page [FC-0112] frontend-app-authoring#2664
• Internal ticket: FAL-4268

Testing instructions

• Follow the testing instructions in: feat: Import Course Details Page [FC-0112] frontend-app-authoring#2664

Deadline

None

Other information

N/A

[openedx-webhooks]

Thanks for the pull request, @ChrisChV!

This repository is currently maintained by @openedx/wg-maintenance-edx-platform.

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.

[navinkarkera]

@ChrisChV I was thinking of updating target field in ModulestoreBlockMigration to allow null values which would indicate failed block migration as mentioned in this openedx/frontend-app-authoring#2523 (comment).

See this commit: 0a675b0

We could add two columns to store block type (optional, can be fetched from meilisearch index in frontend OR extracted from source usage key) and unsupported reason and it could be used in both import details page and to create placeholder blocks openedx/frontend-app-authoring#2527.

If you agree with this plan, I can implement it and you'll need to update the frontend.

@kdmccormick We could use your help here.