feat: Add more granular permissions based on tags

[novakzaballa]

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

• I have run pre-commit to check linting
• I have added information to docs/ if required so people know about the feature!
• I have filled in the "Changes" section below?
• I have filled in the "How did you test this code" section below?
• I have used a Conventional Commit title for this Pull Request

Changes

Based on the issue: #1535

• Tags can now be added to roles to enhance granularity in permissions.

How did you test this code?

To properly test the functionality, this issue must be resolved first.

• Go to the "users and permissions" tab
• Click the "roles" tab
• Select the project where you have the tags you want to manage.
• Select the tags, and click save/update button

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 10, 2024 6:46pm
flagsmith-frontend-preview	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 10, 2024 6:46pm
flagsmith-frontend-staging	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 10, 2024 6:46pm

[github-actions]

Uffizzi Preview deployment-55834 was deleted.

[matthewelwell]

This looks wrong, we need to provide good context here about what adding tags to a role means. Can we link out to some documentation?

[novakzaballa]

I added documentation

[kyle-ssg]

Is there a reason why this is called? seems wrong.

[kyle-ssg]

Looking at this more closely, it does look like this is unnecessary. AddEditTags uses useGetTagsQuery.

[novakzaballa]

You're right, removed.

[kyle-ssg]

I don't understand what this PR does, what does associating tags to a role do?

[kyle-ssg]

I think I understand, so this lets us create a role with permissions but just targets a tagged set of flags?

If so I have further questions that are not indicated by this work, apologies if I'm assuming something wrong:

Presumably only certain permissions are affected by the tags that are selected and the rest aren't?

• If this is the case we need to clearly show what setting these affects, it should be in the permissions tab clearly showing what selecting tags does.

I'm going to assume that this affects Delete feature, Create feature, Update feature state, Create change request and Approve change request?

• If this is the case, isn't it quite a big assumption that all the permissions are for the same tags? It feels like this should be set for each permission otherwise you'd have to create multiple roles with the same users/groups to achieve what you want.

[kyle-ssg]

As discussed, let's hide irrelevant things when opting into tag based permissions

I think we can hide:

• The organisation tab
• Any project in the project tab that isn't the one selected
• Any project and environment features that aren't relevant, including View environment and View Project

[novakzaballa]

I think we can hide:

• The organisation tab

This tab hides when a tag is saved in the role

• Any project in the project tab that isn't the one selected

Projects that do not have the same tags as the role should not be displayed.

• Any project and environment features that aren't relevant, including View environment and View Project

All features that aren't relevant have been hidden.