1. Proposed title of this feature request
GitOps Operator: synchonize ProjectRequests with Projects.

2. What is the nature and description of the request?
A self-provisioner user (without cluster admin rights) is not allowed to generate Project objects directly. Instead, he has to create a ProjectRequest. When that is done, the workflow is the following:

1. The ProjectRequest manifest is added to Git.
2. ArgoCD detects the new manifest and synchronizes it on OpenShift (manually or automatically).
3. When the ProjectRequest object is created on OpenShift, its corresponding Project is created and the ProjectRequest is deleted.

Since then, ArgoCD will consider and show the application status as out of sync because the ProjectRequest in the Git repository does not exist on Openshift.

If somebody tries to synchronize the application again from ArgoCD; the latter will try to create the same ProjectRequest again, but it will fail because its corresponding Project already exists. Therefore, ArgoCD will return a sync failed status.

The request would be that if there is a Project on OpenShift with the same name as a ProjectRequest on a Git repository, the Project object is considered as correctly synchronized by ArgoCD.

3. Why does the customer need this? (List the business requirements here)
The customer would like to allow self-provisioners without cluster admin rights to create Projects (via ProjectRequests) from their ArgoCD instances.

4. List any affected packages or components.
Red Hat GitOps Operator and ArgoCD.