Option to prevent container editing if deployed from a stack?

[havedill]

Is your feature request related to a problem? Please describe

Sometimes people forget that a container was deployed using a stack. For example I just noticed a container was on a higher version than was defined in the stack config. This means someone edited the container directly, which can put things out of sync from what you expect

I could see this being a big problem if say, you edited a containers ENV vars directly, and then went to update the stack, deleting the ENV vars you changed directly. Especially in a business/team setting where there are disconnects

Describe the solution you'd like

I would at least as for a toggle option at least, that prevents editing a container (some sort of warning) saying you need to modify the stack, not the container.

Describe alternatives you've considered

None

Additional context

No response