[FEATURE]: garden-util deployment does not get removed

[jds-harmoney]

Feature Request

Background / Motivation

We are using Garden in CI/CD pipelines, which performs various deploys over a lot of namespaces. This deploys a ton of garden-util deployments in every namespace. Even after all Garden actions this deployment is not needed and could be removed.

What should the user be able to do?

Have an option to remove the garden-util deployment.

Why do they want to do this? What problem does it solve?

At the end of the day our development clusters are scaled down, but sometimes it is not possible as garden-util is still present and costs us money, while this is not needed anymore.

It would make our life a lot easier to have a way of deleting the deployments at the very end of garden. Now we have to take some extra steps in our pipelines to get rid of the deployment multiple times.

Suggested Implementation(s)

Set a flag in the Garden project (or in another place) to remove the garden-util deployment after all actions are completed.

How important is this feature for you/your team?

🌵 Not having this feature makes using Garden painful a bit more expensive.