Add "start/restart" button on the stack details page

[STaRDoGG]

Is your feature request related to a problem? Please describe

I spend an unholy amount of time working with stacks in portainer, and I'm always having to remove 1 or 2 of the services that are running in a stack, and then need to restart them again soon after WITHOUT making any changes to the stack compose code itself, so those servcies I removed get re-added to the running stack.

Currently, that means while on the stack details page I have to always click into the actual editor and click the "update this stack" button each time, which is "clunky behavior" so to speak.

Describe the solution you'd like

If there was simply a start/restart stack button right on the stack details page, basically just the equivalent of the 'update this stack' button, but right on the stack details page as well, it would be super-useful and handy. Just a simple UX tweak.

Somewhere within this yellow circle seems to make the most sense to me, and probably super easy to implement code-wise.

Maybe just to the left of the "stop this stack" button.

Describe alternatives you've considered

Already mentioned above; only other choices are to drill into the editor tab to hit that button.

Additional context

btw, just as a small side note (not a huge deal), I'm always one to try and always "trim the fat" on any UX in hopes of making a UI visually look as less cluttered to the eye and thus less 'noisy and confusing' wherever possible; one tiny thing I see might be to remove the "this" text on those buttons so they're just for example "stop stack", "delete stack", or better yet, just put "stop" and "delete" on them, and use the standard colors added to the theme to visually identify them.

As well as change the redundant "Stack details" header just above it to something like "stack control" or the like, since "Stack details" is also in an even bigger header just above it. Also, those stack control buttons aren't really "details".

Update: I threw togetehr a quick UI mockup for the stack details page that makes the most sense to me, if anyone is interested:

Nothing big, just my personal opinion based on around 30 years of UI dev. :p

Update:

While on the subject, I threw together a quick (and ugly) UI mockup for the stack details page that makes the most sense to me, if anyone is interested: