Description of Problem

• Within Argo CD operator we allow users to specify ArgoCD CR fields that will install principal-configuration of argocd-agent
• However, at present, we are not creating the resource proxy k8s Service which is required to proxy resource traffic from principal to individual agents.
• An example Service for this is available here: https://github.com/argoproj-labs/argocd-agent/blob/main/install/kubernetes/principal/principal-resource-proxy-service.yaml

Acceptance Criteria

• Update the argocd-operator code to create a Service that points to resource proxy endpoint of agent Deployment
• My expectation is that this should be created in all case (e.g. the resource proxy is an essential part of argocd-agent, so I don't think there would ever be a case where the Service should not be created)
• We don't need to expose the Service via LoadBalancer or Route
• Unit/E2E tests to verify functionality