feat: disallow edits to units in courses that are sourced from a library

[rpenido]

Description

This PR disallows edits to units in courses (including title change, children change) that are sourced from a library.

Supporting information

• Implements Disallow edits to units in courses that are sourced from a library #1712
• Depends on feat: disallow edits to units in courses that are sourced from a library [FC-0083] openedx-platform#36558

Testing instructions

• Open a unit that was added from a library (feat: Add unit from library in course [FC-0083] #1829)
• Checkout feat: disallow edits to units in courses that are sourced from a library [FC-0083] openedx-platform#36558
• Check that the Edit (near the title) is disabled
• Check that the "Publish" button on the sidebar is disabled
• Check that the "Manage Tags" button on the sidebar is disabled
• Check that you cannot add new blocks to the unit
• Check that you cannot change the children blocks on the unit

---

Private ref: FAL-4112

[openedx-webhooks]

Thanks for the pull request, @rpenido!

This repository is currently maintained by @openedx/2u-tnl.

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

All modified and coverable lines are covered by tests ✅

Project coverage is 93.76%. Comparing base (d6b51ec) to head (1ff27c5).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1833      +/-   ##
==========================================
+ Coverage   93.74%   93.76%   +0.01%     
==========================================
  Files        1146     1146              
  Lines       23824    23881      +57     
  Branches     5022     5030       +8     
==========================================
+ Hits        22334    22391      +57     
  Misses       1422     1422              
  Partials       68       68              

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

[pomegranited]

@rpenido I had to fix a few things on the Course Outline page, and made sure that we're only disallowing edits on Units sourced from a library (lct:...).

Also -- we still need to be able to publish Units sourced from a library, we just can't edit them.

But this is working enough for now :)

TODO in a follow-up PR:

• If the upstream link is broken, allow edits.

👍

• I tested this using the PR test instructions on : units sourced from a library are read only, units copy/pasted from a course are editable, normal units are editable.
• I read through the code
• I checked for accessibility issues by using my keyboard to navigate
• Includes documentation -- code docs
• User-facing strings are extracted for translation

[ChrisChV]

Looks good!