fix(argo-cd): Fixed default tls hosts for grpc ingress endpoint

[groundhog2k]

The default tls hosts entry for ingress must match the default ingress rules host - which can be .Values.server.ingressGrpc.hostname or $hostname when nothing else was specified.

Example to reproduce this bug:

Create a server with 2 ingresses (for argocd ui and grpc):

global:
  domain: "argocd.k8s.local"

server:
  ingress:
    enabled: true

    annotations:
      cert-manager.io/cluster-issuer: blablabla

    tls: true
    hostname: "argocd.k8s.local"

  ingressGrpc:
    enabled: true
    annotations:
      cert-manager.io/cluster-issuer: blablabla
      nginx.ingress.kubernetes.io/backend-protocol: "GRPC"

    tls: true
    hostname: "argocd-grpc.k8s.local"

The Argo CD UI ingress endpoint is correct.

The GRPC ingress endpoint will be rendered with wrong tls hosts path (grpc.argocd.k8s.local
instead of argocd-grpc.k8s.local).

The PR will fix this problem.

---

Checklist:

• I have bumped the chart version according to versioning
• I have updated the documentation according to documentation
• I have updated the chart changelog with all the changes that come with this pull request according to changelog.
• Any new values are backwards compatible and/or have sensible default.
• I have signed off all my commits as required by DCO.
• My build is green (troubleshooting builds).

[mkilchhofer]

@pdrastil can I have your eyes on this as you refactored the whole Ingress piece? :-)

[pdrastil]

LGTM - thanks for extra fallback