chore: deprecate content libraries authorization permissions, apis, rest apis and models

[BryanttV]

Description

This PR deprecates the Content Libraries team roles/permission system backed by the ContentLibraryPermission model, following OEP-0021.

Concretely, this PR:

• Marks the ContentLibraryPermission model as deprecated via docstring and a DeprecationWarning.
• Marks the Content Libraries authorization/team REST API endpoints as deprecated in their docstrings and via a module-level DeprecationWarning.
• Marks the authorization API methods in openedx/core/djangoapps/content_libraries/api/libraries.py as deprecated (get_library_team, get_library_user_permissions, set_library_user_permissions, set_library_group_permissions) with a DeprecationWarning on each call.
• Marks the legacy permission rules and constants in permissions.py (and the re-exports in api/permissions.py) as deprecated in their module docstrings, in favor of openedx-authz and HasPermissionInContentLibraryScope.
• Removes the ContentLibraryPermission inline from the ContentLibrary Django admin so new permissions are no longer managed through that model.

Supporting information

• [DEPR]: Libraries' Roles and Permission System #37409
• Discuss Post

Deadline

None

[openedx-webhooks]

Thanks for the pull request, @BryanttV!

This repository is currently maintained by @openedx/wg-maintenance-openedx-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.

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.

[feanil]

Looking for some more clarification, the DEPRs make sense but it would be useful to point to more actionable docs for what to do when you see this warning. Where are the new APIs documented?

[feanil]

Pointing to the DEPR is useful but if I saw this, I still wouldn't easily know what api endpoint things would need to switch to. Is there a new equivalent endpoint? Or is there a set of endpoints that I need to use? Is there a quick reference or doc I could look at to know what I should switch to if I've been calling this endpoint?

[BryanttV]

Thanks for the feedback! I completely agree. I’ve updated the deprecation messaging, including the replacement of each api method or view.