AB#135264 improv resource permissions

[Maximo-reliefapps]

Description

Changelog:

• Adding CanSeeRecords / CanEditRecords permission will now automatically update the state of the field permissions.
• Updating a permission will now show a loader in the middle of the permissions table. On successful update a snackbar will show a success message.
• There's now a multi-selection option for fields on a resource, you can select multiple fields to give CanSeeRecords / CanEditRecords permissions. The behavior is to mark all as true by default, and if all selected are already true, mark them as false (reflected on the button icons + tooltips).
• There's now an option to auto grant permissions to fields in resources. The options will be selected by default and you can toggle them off on the resource settings. Existing fields wont be impacted.

Useful links

• #135264 ABC - Improve usability of permissions on resources
• Frontend PR

Type of change

• Improvement (refactor or addition to existing functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

• In a project, go to permissions, select a resource and give it a permission. All fields should update with the given permission.
• In a project, go to permissions, select a resource and give it a permission. You should see a loader while updating + a snackbar confirming the change.
• In a project, go to permissions, select a resource, on the fields select multiple fields and click on the header to give a permission to all selected fields. Do the same to remove the permission.
• In a project, go to permissions, select a resource. If the resource has any permission you should see the auto-grant check box selected. You can then add a field to the resource, and when getting back to the project permissions the new field should have the same permission as the resource. You can uncheck the checkbox to avoid that.

Screenshots

Checklist:

( * == Mandatory )

• * I have set myself as assignee of the pull request
• * My code follows the style guidelines of this project
• * Linting does not generate new warnings
• * I have performed a self-review of my own code
• * I have put the ticket for review, adding the oort-frontend team to the list of reviewers
• * I have commented my code, particularly in hard-to-understand areas
• * I have put JSDoc comment in all required places
• * My changes generate no new warnings
• * I have included screenshots describing my changes if relevant
• * I have selected labels in the Pull Request, according to the changes with code brings
• I have made corresponding changes to the documentation ( if required )
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

More explanation

https://www.loom.com/share/05a716d61b9744faaf51fb304c21d1e5?sid=f87cf896-582a-4f76-93ae-8ceed801b145