Support referencing existing webhook TLS Secret by name

[alita1991]

Describe the feature you are requesting

Allow the AWS Load Balancer Controller webhook to consume an existing Kubernetes TLS Secret by name directly, without requiring to read or embed the certificate contents (ca.crt, tls.crt, tls.key) from values or via template lookups.

Motivation

• The current approach works only when Helm has direct access to the cluster during render time.
• In GitOps-managed environments (e.g., ArgoCD), the lookup function fails silently because ArgoCD does not execute live cluster lookups.
• This prevents the webhook from mounting or referencing an existing TLS secret, breaking automated and declarative deployments.

webhookTLS:
  caCert:
  cert:
  key:

Describe the proposed solution you'd like

webhookTLS:
  existingSecretName: my-webhook-tls

[kellyyan]

Hi, this is a valid feature request. We welcome any community contributions.