feat(argo-cd): Adding "appProtocol" to HTTP service port of argocd-server

[gaffneyd4]

Make it possible to configure appProtocol for the http port.

Motivation: Supports use case of configuring prior knowledge h2c for gRPC support (used by argocd CLI) when argocd-server is not configured to listen with HTTPS (--insecure). When configured properly, proxies like envoy and istio support HTTP/2 "prior knowledge" (h2c) for upstream connections (istio example).

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.
• I have created a separate pull request for each chart according to pull requests
• My build is green (troubleshooting builds).

[gaffneyd4]

I just noticed that this PR might possibly duplicate the efforts in #3585

[gaffneyd4]

The existing HTTP port needs to remain supporting HTTP/1.1 for handling requests from the browser. Unencrypted HTTP can't support both HTTP/1.1 and prior knowledge h2c. The correct approach will be to add an extra port for h2c that gRPC can use (or optionally repurpose the https port for h2c gRPC use when the server is running with --insecure mode).