Add the ability to disable the automatic ingress links

[jbonjean]

Summary

It would be useful to have a way to disable the automatic ingress links so we can have more control over what is displayed in the UI.

Motivation

• I have ingresses that define some paths that send the traffic to an "error backend" (its job is to only send a HTTP 4xx/5xx errors). I don't want these paths to show up in the ArgoCD UI. This may be a weird setup, but I'm sure there are other unusual setup out there that cannot be automatically detected.
• This would provide a possible workaround for issues like ArgoCD UI Ingress go-to links use wrong URL scheme (HTTP) #8021.

Proposal

A new annotation that can be put on ingress resources could allow the user to disable the automatic URL generation logic. Manually provided external URLs (link.argocd.argoproj.io/.. annotations) should still be processed, allowing the user to chose exactly which URLs should be displayed.

[colinodell]

We have hundreds of applications with dozens of Ingress URLs each. Loading /applications in the Argo UI takes a good 20-30 seconds to load because of all the URLs it's trying to render. Being able to disable the automatic ingress links would immediately solve this problem for us.