Removing role functionality on audit user page

[jacobo-dominguez-wgu]

Description

Adding the delete role functionality to the roles table on audit user view.
The table shows a different remove button icon depending on:

• Non clickable info icon for django roles, showing a tooltip when hovered.
• A disabled trash icon button for admin roles (library_admin or course_admin) in case a user is on his own specific user page (preventing to remove its own admin roles).
• Regular trash icon for the rest of the scenarios.

It closes #89
Figma design

⚠️ Includes code from #106, needs to be reviewed after it.

Pending things:

• Unit testing. ✅
• Integration with API when is ready. ✅
• A couple of TODOs. ✅

Warning

Will be on draft status until the required endpoints are completed.
This PR requires some the endpoints proposed in the section "Proposed Endpoint for M2"

How to test it

Pre - requisites

A running local tutor instance.
It requires the endpoint created on this PR openedx/openedx-authz#230 to fetch the table data

1 - Go to the new audit user page -> http://apps.local.openedx.io:2025/admin-console/authz/user/:username (select a user with many roles assigned to get a more populated table) (NOTE: The team members table will redirect to this page, currently in progress #124)
2 - Verify the actions icon button shows according the described scenarios:

• Non clickable info icon for django roles (superadmin, globalstaff), showing a tooltip when hovered.
• A disabled trash icon button for admin roles (library_admin or course_admin) in case a user is on his own specific user page (preventing to remove its own admin roles).
• Regular trash icon for the rest of the scenarios.

3 - Click on the trash icon and must appear a confirmation modal.
4 - Confirm the removal, the modal gets closed, a toast shows success message and the entry row gets removed from the table.

[openedx-webhooks]

Thanks for the pull request, @jacobo-dominguez-wgu!

This repository is currently maintained by @openedx/committers-frontend.

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 98.94737% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 95.88%. Comparing base (411e3d3) to head (8d11260).
⚠️ Report is 2 commits behind head on master.

Files with missing lines	Patch %	Lines
src/authz-module/data/api.ts	85.71%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #108      +/-   ##
==========================================
+ Coverage   95.70%   95.88%   +0.17%     
==========================================
  Files          69       70       +1     
  Lines        1536     1602      +66     
  Branches      321      341      +20     
==========================================
+ Hits         1470     1536      +66     
  Misses         64       64              
  Partials        2        2              

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

[arbrandes]

This depends on #106, so I'm converting to draft.

[jacobo-dominguez-wgu]

@dcoa This one is now ready for review, could you take a look?

[dcoa]

This is a very light review so I can not approve

[rodmgwgu]

Tested in my local, functionality works fine, just found an issue that may not be directly related to this PR:

After removing a role from a user, and navigating back to the Team Members page using the link in the breadcrumbs, the user still appeared there (did not reload the data on the Team Members page), perhaps we should invalidate that data on role removal.

[jacobo-dominguez-wgu]

Tested in my local, functionality works fine, just found an issue that may not be directly related to this PR:

After removing a role from a user, and navigating back to the Team Members page using the link in the breadcrumbs, the user still appeared there (did not reload the data on the Team Members page), perhaps we should invalidate that data on role removal.

Thanks for testing it. I have fixed this issue in the latest commit!

[rodmgwgu]

Tested it again and all is working correctly, just added some nit comments. Thanks!

[rodmgwgu]

Looks good, thanks for addressing my comments!

[jacobo-dominguez-wgu]

Will wait a bit before merging it.