Description of problem:

The application controller controller is spamming the logs about failing to establish a watch on the OpenShift Project API.

time="2024-08-09T19:18:32Z" level=info msg="Start watch Project.project.openshift.io on https://172.30.0.1:443" server="https://kubernetes.default.svc"90time="2024-08-09T19:18:32Z" level=info msg="Failed to watch Project.project.openshift.io on https://172.30.0.1:443: initial RV \"\" is not supported due to issues with underlying WATCH, retrying in 1s" server="https://kubernetes.default.svc"91E0809 19:18:32.728128 1 retrywatcher.go:130] "Watch failed" err="unknown" 

This does not appear to hinder functionality in any way but it is irritating for users managing an Argo CD installation.

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

I'm noticing this when using respectRBAC but it has been seen in other circumstances as well. 

1. Enable resource.resource,respectRBAC in extraConfig
2. Configure additional clusterrole and clusterrolebinding if using a cluster scoped instance
3. Check the logs to see the above message. 

Actual results:

Log being spammed with message shown previously

Expected results:

No spamming of the logs

Reproducibility (Always/Intermittent/Only Once):

Always with right configuration

Acceptance criteria: 

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

 *