[Feature] Add tag and group functionality to stacks

[callumgare]

This issue proposes adding tag and group functionality to stacks, similar to what already exists for endpoints.

I have over 40 stacks and managing them is starting to become a bit unwieldy. I'd love to be able to be able to group stacks as well as tag them. For example I have a variety of stacks responsible for networking infrastructure (traefix, authelia, etc) and it would be great to be able to group them together.

Another use case is finding stacks with obscure names. I have a number of different stacks running web-based file browser services. The stacks are named the same as service they run. So one of them is called "h5ai" and another is called "gossa". I use those services infrequently so when I do go pull them up I struggle to remember their names. I find myself wishing I could just select a "file browser" tag or group and pull up all a list of all those stacks.

Part of this would be including a view to show all groups and/or tags of which clicking on an item would take you to the standard view for stacks but filtered by that group/tag.

Maybe instead of adding two separate entities ("tags" and "groups") this could be implemented by just adding a "groups" entity but a stack can belong to multiple different groups.

[SvenDowideit]

very much agreed - IMO it would be excellent to push this kind of functionality into the table component, and then use that everywhere

see also: #5253 #5370 #3129 #2839 #1960 #785 #568

[charles-997]

I agree with this UX improvement.
I do not manage services via the containers view- I primarily use the stacks view. I do all the management via docker compose files in a git repo, the stacks reference said file, and I can start stop and manage services from the stacks view.
Due to the current UX, I cannot tag the stacks as "production" vs "testing" or any other tags. It would be fantastic to be able to select all stacks with a certain tag, say "testing", and start or stop all at once.

[jimmygle]

Would love to see this feature.

[MarcusElevait]

+1
In my current company, we want to provide a deployment self-service tool. This tool will do a lot of things, but one of these things is to handle stacks via the portainer api.
Now we want to distinguish the stacks between those who're created via this tool and those who're not.

[nedmiles1]

Adding a +1 for this