Would like the ability to define a helm version retention threshold like a MaxHistory

[brianrexrode]

Is your feature request related to a problem? Please describe.

For long-lived clusters deploying zarf packages, helm.release secrets continue to pill up and are only removed manually

Describe the behavior you'd like

• Given I deploy numerous zarf packages to a long-lived cluster
• When I define a MaxHistory threshold (or similar)
• Then previous versions of helm.release secrets are deleted

Describe alternatives you've considered

(optional) Adding a kubectl command to a uds task to delete the older secrets

kubectl delete secret -n <namespace> -l "owner=helm,status=superseded"
kubectl delete secret -n <namespace> -l "owner=helm,status=failed"

Additional context

An easy way to reproduce the issue is to deploy and redeploy zarf packages.
Quick test option:

uds deploy k3d-core-slim-dev:latest --confirm

for i in {1..5}; do
    zarf package deploy oci://ghcr.io/defenseunicorns/packages/uds/core-metrics-server:0.31.2-upstream --confirm
done

kubectl get secrets -n metrics-server