[FC-0099] feat: assign library roles after successful library creation

[mariajgrimaldi]

Description

This PR grants the library_admin role to a user after they create a content library. The assigned role matches the current access level defined in the migration plan: https://openedx.atlassian.net/wiki/spaces/OEPM/pages/5252317270/Libraries+Roles+and+Permissions+Migration+Plan. This ensures the user keeps the same level of access in the new authorization framework.

This PR only handles the role assignment. The actual permission checks for this new role will be added in a separate PR, so this one has no functional effect yet.

The upcoming PR that introduces these checks, along with other roles related to the Administration Console experience, is here: #37501. The integration with the Authoring MFE, where this role will take effect, is still a work in progress. I'll link it here once it's ready.

Supporting information

openedx/openedx-authz#111 (comment)
https://github.com/openedx/openedx-authz/?tab=readme-ov-file#openedx-authz
https://discuss.openedx.org/t/depr-libraries-roles-and-permission-system/17392

Testing instructions

1. Login into studio with course creator permissions, then create a library from scratch
2. You can use the openedx-authz REST API to get all roles for users, and review whether the role was assigned to the user you just used: http://local.openedx.io:8000/api-docs/#/authz/authz_v1_roles_users_list, where scope is the ID of the library you just created

[openedx-webhooks]

Thanks for the pull request, @mariajgrimaldi!

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.

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.

[mariajgrimaldi]

So I don't lose this: https://openedx.atlassian.net/wiki/spaces/OEPM/pages/5252317270/Libraries+Roles+and+Permissions+Migration+Plan

[mariajgrimaldi]

I have a unittest I need to push :)

[bmtcril]

Looks good to me!

[rodmgwgu]

Looks good, thanks!

[MaferMazu]

Looks good to me