Allow configure-sso job to use existingSecretName

I’d like to request a modification to the Helm chart regarding the configure-sso job. Currently, the job references the secret name using {{ template "enterprise.fullname" . }}, which results in the job looking for a secret named anchore-enterprise-anchore-enterprise.

In our deployment, we are using the existingSecret configuration, but the current behavior does not honor this setting. As a result, the configure-sso job fails when it cannot find the expected secret name.

Could the chart be updated so that the configure-sso job supports the existingSecret value if it is defined? This would improve flexibility and consistency with other parts of the chart that already support this pattern.