feat: Enable dedicated grpc ingress for argo-cd-server (#367)

* [argo-cd] Enable dedicated grpc ingress

This is based on the information found at
https://argoproj.github.io/argo-cd/operator-manual/ingress/

* [argo-cd] Ensure unique name for grpc ingress

* [charts/argo-cd]  Bump chart version

charts/argo-cd/values.yaml

@@ -452,6 +452,29 @@ server:
       # - secretName: argocd-example-tls
       #   hosts:
       #     - argocd.example.com
+    https: false
+  # dedicated ingess for gRPC as documented at
+  # https://argoproj.github.io/argo-cd/operator-manual/ingress/
+  ingressGrpc:
+    enabled: false
+    annotations: {}
+    labels: {}
+
+    ## Argo Ingress.
+    ## Hostnames must be provided if Ingress is enabled.
+    ## Secrets must be manually created in the namespace
+    ##
+    hosts:
+      []
+      # - argocd.example.com
+    paths:
+      - /
+    tls:
+      []
+      # - secretName: argocd-example-tls
+      #   hosts:
+      #     - argocd.example.com
+    https: false
 
   # Create a OpenShift Route with SSL passthrough for UI and CLI
   # Consider setting 'hostname' e.g. https://argocd.apps-crc.testing/ using your Default Ingress Controller Domain