Update/Clean Up User Management & Add Revoke

[qhanson55]

Description

1. Cleaned up functionality for User Management View/ Table.
2. Changed flow for Admin users so that they have one table for managing users and one for managing user access/revocation requests. See FIGMA
3. Added ability to revoke users
4. Cleaned up Create User Modal

These changes help with the functionality of user maangement table and solves refreshing issues, creates a cleaner flow for admins users, allows users' access to be revoked by Admins and Supervisors to request revocation, and better usability for creating users.

PADS-257
PADS-309

Types of changes

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING doc
• I have checked that unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[github-actions]

Coverage Report (Frontend)

Totals
Statements:	25.01% ( 1590 / 6358 )
Methods:	20.33% ( 223 / 1097 )
Lines:	29.46% ( 920 / 3123 )
Branches:	20.91% ( 447 / 2138 )

[github-actions]

Coverage Report (Application)

Totals
Statements:	36.43% ( 966 / 2652 )
Methods:	26.22% ( 118 / 450 )
Lines:	47.43% ( 647 / 1364 )
Branches:	23.99% ( 201 / 838 )

[slhurley]

Is it possible to make the actual name field highlighted and ready for entry when you go into "Create new user" without having to click there first? It also looks like you can have more than one role? I thought they were elevated privileges and you could only have one role at a time? I'm not sure how I did it but at one point I had a user with 3 roles showing in the list. Also if you try to grant a role that they already have you get an Error popup but no useful error message. Biggest issue is that it seems the User Access Requests no longer works? The privileges between Admins and Supervisors seem to be exactly the same?

[kyle1morel]

General note, not asking for any changes at this time. New/update verbiage should be added to the en-CA.json file, and the text referenced via i18n. I will be asking for this to happen in future PRs.