[UIROLES-125] Remove unused sub-permissions and add "manage" permission set.

[ryandberger]

• Fulfills UIROLES-125.
• Removed unused or duplicate permissions.
• Added new "manage" permission set which allows users to view and assign users to roles.
• Enforcement of "manage" permission is handled in [UISAUTHCOM-39] Enforce new "manage" permission set  stripes-authorization-components#60.

[github-actions]

Jest Unit Test Results

1 files  ±0  2 suites  ±0   22s ⏱️ -1s
7 tests ±0  7 ✅ ±0  0 💤 ±0  0 ❌ ±0 
8 runs  ±0  8 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit dca0e71. ± Comparison against base commit 9e66664.

♻️ This comment has been updated with latest results.

[zburke]

LGTM, but we need to be certain about the delete behavior

[zburke]

Are role assignments automatically deleted by cascade when a role is deleted? If so, fine. If not, then either

1. this permission needs to stay so that we can issue the requests to delete them, and then delete the role
2. this permission goes, and we need to add logic in the application to hide the delete button when the user has ui-authorization-roles.settings.delete, AND does not have permission to manage role assignment, AND the role has one or more users assigned

[ryandberger]

According to the JIRA ticket description UIROLES-125 for roles.users.item.delete:

"NOTE:  the backend handles this... when deleting a role the UI shouldn't (as AFAICT doesn't) first remove role/user assignments associated with the role being deleted."

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud