Prevent UI access to members on projects if they don't have the correct permissions

[aalves08]

To Reproduce

1. Create a user testuser as a standard user
2. Create a project called proj-owner and add testuser as a member with the role Project Owner
3. Create a project called proj-manage-member and add testuser as a member with the role Manage Project Members
4. Create a project called proj-view-member and add testuser as a member with the role View Project Members
5. Create a project called proj-view-catalog and add testuser as a member with the role View Project Catalog
6. login as testuser and check UI for edit config for each project

Result Several inconsistencies with UI being enabled, especially for managing members, where the edit interface is available when it shouldn't be

Expected Result 2) Edit interface for both Project and Members available and unblocked for input 3) Edit interface for Members available and unblocked for input, Project interface blocked for input 4) Edit interface for both Project and Members blocked for input 4) Edit interface fore Members not available, Project interface blocked for input

[aalves08]

Waiting on https://github.com/rancher/dashboard/issues/5722 for this to possibly move forward (will need re-evaluation)

[richard-cox]

@aalves08 Can this be closed? Blocking issue is still open (https://github.com/rancher/dashboard/issues/5722) and has been tracked for a possible solution via SURE-6164

[aalves08]

Yes, let's do it. This PR is so old that we wouldn't be able to use it anyway.