feat: add unlink upstream menu [FC-0097]

[rpenido]

Description

This PR adds the Unlink feature to the Course Outline for Sections, Subsections and Units.

Useful information to include:

• Which user roles will this change impact?
  "Course Author",

Supporting information

• Related to:
  • Course Outline: Add unlink from library #2164
  • Course Outline Unlink Dialog #2380

Testing instructions

NOTE: This feature needs the top-parent level logic, so it can cause inconsistencies and will not work correctly with containers imported before openedx/openedx-platform@a1195ef

• Create a nested Section, Subsection, Unit structure in a library and publish it
• Create a new course and add the section to this course
• Make some changes to the Section and Subsection on the library and publish both again
• You can check that only the Section will be shown on the Content -> Library Updates page
• Unlink the Section using the 3-dot menu on the Course Outline
• Check that the page is refreshed and the library sync icon is removed from the Section
• You can check that not only the Subsection will be shown on the Content -> Library Updates page

Other information

• Depends on: feat: Add unlinkable to xblock actions and update top_level_parent_key on unlink [FC-0097] openedx-platform#37215

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'

---

Private ref: FAL-4225

[openedx-webhooks]

Thanks for the pull request, @rpenido!

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.04762% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 94.60%. Comparing base (0c88fd6) to head (e23e99d).
⚠️ Report is 11 commits behind head on master.

Files with missing lines	Patch %	Lines
src/generic/key-utils.ts	85.71%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2393      +/-   ##
==========================================
+ Coverage   94.55%   94.60%   +0.04%     
==========================================
  Files        1174     1179       +5     
  Lines       25366    25506     +140     
  Branches     5551     5574      +23     
==========================================
+ Hits        23984    24129     +145     
- Misses       1313     1314       +1     
+ Partials       69       63       -6     

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

[navinkarkera]

@rpenido Looks good, Thanks! 👍

• I tested this: (Unlinked different levels of blocks)
• I read through the code
• I checked for accessibility issues
• Includes documentation

[ChrisChV]

Great work! @rpenido Looks good! 👍 Only I left one nit

[ChrisChV]

Is it duplicated?

[rpenido]

This was already tested in other places, but for completeness, I updated this test here: e23e99d