auth policy conflict if multiple packages use wrapper in the same namespace

Bug

Description

If you have multiple packages utilizing wrapper in the same namespace, only 1 of those packages can successfully complete the helm install.

Other packages will see errors like this:

Warning InstallFailed 9m (x97 over 21h) helm-controller Helm install failed for release morpheus/mlflow-wrapper with chart wrapper@0.4.10+ae0e0e46c196: Unable to continue with install: AuthorizationPolicy "allow-all-in-namespace" in namespace "morpheus" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "mlflow-wrapper": current value is "ai-engine-wrapper"

For the log above, here is a partial snippet of my values that contributed to this error:

packages:
  ai-engine:
    enabled: true
    namespace:
      name: morpheus
      create: false # must be false the ns can only be created once and mlflow already does so
      labels: {}
      annotations: {}
    wrapper:
      enabled: true
    helmRelease:
      namespace: morpheus
    monitor:
      services:
        - spec:
            endpoints:
              - port: http
  mlflow:
    enabled: true
    namespace:
      name: morpheus
      create: true
      labels: {}
      annotations: {}
    wrapper:
      enabled: true
    helmRelease:
      namespace: morpheus

It is also entirely possible that I am doing something wrong as an end-user.

BigBang Version

What version of BigBang were you running?

2.38.0 with wrapper@0.4.10