feat: Copy tags when sync library [FC-0062]

[ChrisChV]

Description

This PR adds:

• Call copy_tags function of tagging API to copy tags from all library components when adding (copy) a library in a course.
• Update ObjectTagMinimalSerializer to avoid delete tags that are copied.
• Which edX user roles will this change impact? "Course Author"

Supporting information

• Github issue: Copy tags when using content from a V2 Library in a Course modular-learning#177
• Depends on: feat: Copy object tags [FC-0062] openedx-learning#236
• Internal ticket: FAL-3616

Testing instructions

• Run this script to create taxonomies: https://github.com/open-craft/taxonomy-sample-data
• Run make requirements in lms and cms shell or rebuild your openedx-dev image in tutor.
• To test this you need to use the legacy Unit page (disable contentstore.new_studio_mfe.use_new_unit_page)
• Create a new library with components. Add tags to these components.
• Copy to Clipboard a component
• Go to a unit inside a course.
• Paste the component. Refresh the page to see tags count button.
• Open the manage tag, verify the copied tags. Edit and verify that you can't delete.
• Add more tags and verify that you can delete the new added tags.
• On the library, add more tags to the component. Edit the component and update the title.
• Return to the course and refresh the page.
• Click on "Update Available" of the new component.
• Verify the new tags.
• On the library add the same tags of the component in the course. Edit the component and update the title.
• Return to the course and refresh the page. Click on "Update Available" of the new component.
• Verify the new tags and verify that you cant delete the tags

Deadline

ASAP

Other information

Before merge:

• Bump openedx-learning version: feat: Copy object tags [FC-0062] openedx-learning#236

[openedx-webhooks]

Thanks for the pull request, @ChrisChV!

What's next?

Please work through the following steps to get your changes 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.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/wg-maintenance-edx-platform. Tag them in a comment and let them know that your changes are ready for review.

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 Nice job! 🚀

• I tested this: (Played around with tags in library and course via library component and verified the tags after sync.)
• I read through the code
• I checked for accessibility issues
• Includes documentation

[bradenmacdonald]

@ChrisChV I guess this has needed some refactoring since I last reviewed it, so let me know when it's ready for another review.

[ChrisChV]

I guess this has needed some refactoring since I last reviewed it, so let me know when it's ready for another review.

@bradenmacdonald Yes, the way to copy components has changed. It's ready for a new review.

[bradenmacdonald]

One suggestion... otherwise I'm just testing now and then I'll approve.

[bradenmacdonald]

I tested this and it works great! The only weird thing is that since tags aren't part of the draft-publish cycle, you have to make changes to the block and publish them before the tags will be synced. We should mention that to the product team during acceptance testing.

Please consider making the changes I suggested before merging, but go ahead and merge either way.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.