allow use custom secret

[templarfelix]

• add parameter gremlin.secret.create for allow helm create secret
• if need use custom secret set gremlin.secret.create = false and set custom gremlin.secret.name example: my-custom-secrets

example for this case: allow use external secrets for create secret using secretManager

apiVersion: kubernetes-client.io/v1
kind: ExternalSecret
metadata:
  name: custom-gremlin-secrets
spec:
  backendType: secretsManager
  region: sa-east-1
  data:
    - key: /v1/gremlin/sa-east-1/secrets
      name: GREMLIN_TEAM_SECRET
      property: GREMLIN_TEAM_SECRET
    - key: /v1/gremlin/sa-east-1/secrets
      name: GREMLIN_CLUSTER_ID
      property: GREMLIN_CLUSTER_ID
    - key: /v1/gremlin/sa-east-1/secrets
      name: GREMLIN_TEAM_ID
      property: GREMLIN_TEAM_ID

[thefirstofthe300]

I think we'd prefer not to go about creating a new secret type based on whatever management system a customer is using as it would lead to proliferation of different unused resources we'd need to maintain. What would prevent you from referencing the secret created by the External Secrets controller using the gremlin.secret.name value?