Add view_identities permission

[kyle-ssg]

Thanks for submitting a PR! Please check the boxes below:

• I have run pre-commit to check linting
• I have filled in the "Changes" section below?
• I have filled in the "How did you test this code" section below?

Changes

Assuming the view_identities_permission feature is enabled:

• Users with VIEW_IDENTITIES can view the users aside nav
• Users with MANAGE_IDENTITIES can delete an identity, it will be disabled for VIEW_IDENTITIES permissions
• Users with VIEW_IDENTITIES can see a read only view of the identity detail page
• Users with MANAGE_IDENTITIES can edit a users feature states, this used to be based on UPDATE_FEATURE_STATE

[github-actions]

Uffizzi Preview deployment-9339 was deleted.

bug found

[matthewelwell]

It seems like this has had an effect on users with VIEW_ENVIRONMENT permissions from viewing Change Requests?

To reproduce:

• Create a user with VIEW_PROJECT and VIEW_ENVIRONMENT permissions
• Login with that user and try to view the Change Requests page

This might be unrelated to this PR but I've tested and it doesn't happen in production or staging.

[matthewelwell]

The above is unrelated to this PR - it's caused by the fact that the preview environment is built without the change request views (as they are contained in a separate private repository and bundled into the application at build time for SaaS / private cloud build workflows).

[matthewelwell]

In testing this, I've noticed a few issues:

• Tooltips for delete identity and 'Add New Trait' buttons show that the user needs the 'update feature state' permission, rather than 'manage identities' (screenshots below)
• Tooltip for 'Create Users' button shows that the user needs 'Admin' for the environment but should show 'manage identities' (screenshot below)
• When an identity has no traits, I am able to click on the 'Add New Trait' button (note: this is not the case when the identity already has traits). It looks like this works too because the FE is using the SDK endpoint rather than the admin endpoint.
• Delete trait button is clickable and tries to delete the trait but fails silently with a 403 error on the API (which is correct)

[matthewelwell]

Approved but I've created #1819 to track issue related to point 3 above.