Route path parameter support not implemented

[trewallier]

Describe the bug
The ArgoCD resource has an option to set the spec.server.route.path parameter, which is well documented. Although, the config value is not respected by the operator as the route controller implementation does not use the Route path at all.

To Reproduce
Steps to reproduce the behavior:

1. Deploy an ArgoCD instance with Path configured in server Route

Expected behavior
ArgoCD operator should set the spec.server.route.path parameter as defined and documented in the ArgoCD resource spec.
Additional expectation: by default ArgoCD server cannot serve on subpath, additional server arguments (server.basehref, server.rootpath) have to be configured if Route/Ingress path is configured. See ArgoCD docs for more details.

Screenshots
Can be added later if description and context is not clear.

Additional context
Route support was introduced in #100. According to the changelog it is clear that only the Grafana component's Route resource respect the Path (search for route.Spec.Path), but the server and the Prometheus component does not. Since then the Grafana component was deprecated so the documented Path parameter is not respected now in the reconcile loop, as the implementation is missing.