CRDCDH-2105 PBAC – Individual Permissions Control of User Accounts

[amattu2]

Overview

This PR introduces the ability to configure individual PBAC permissions for an account.

Warning

Some known issues / expected things from the backend implementation:

• You can adjust a Submitter or User's permissions, but no changes will actually be saved. This is expected, but BE should be locking all permissions, and they currently aren't
• The backend seems to reject some permissions and/or notification selections and returns an error for it. Just uncheck them in the FE for now
• The visual permission names don't really match the user stories anymore (they keep getting changed)
• The order of actual permissions in the nested groups may not match the user stories (see below)

Note

The frontend sorts the groups based on the User Story, but we don't sort the nested permissions themselves since that's somewhat impractical (way too many options).

Change Details (Specifics)

• Implement a PermissionsPanel component, which handles the PBAC checkboxes, defaults, and form management
• Update the useProfileFields hook to conditionally render permissions/notifications fields
• Update remaining queries to pull the notification/permission assignments
• Update the Apollo memory cache to stop it from normalizing the PBAC data
  • It was discarding the relationship between the roles and their specific defaults causing serious issues
• Move AuthPermissions to a separate file (PBAC.d.ts) and create AuthNotifications type for consistency
  • I'm also fine with just leaving it in Auth.d.ts if that's preferred, it was just getting cluttered
• Update the ProfileView action buttons to be consistent with design (matching DS and SR theme)

Related Ticket(s)

CRDCDH-2105 (Task)
... A lot of stories

[Alejandro-Vega]

Code looks solid, and I like the changes you made with separating the PBAC types to their own file. I left a few super small and optional suggestions. Feel free to disregard them.