Description of problem:

Application "Clusters" Field shows "None" on Application Page once upgrade and GitOps Workaround is Applied. 

When you have an existing Openshift Gitops operator installed and you upgrade to version 1.17, you will encounter a forbidden permission error in the ApplicationSet resource status.
To workaround this issue, delete the RoleBinding resource `openshift-gitops-applicationset-controller-placement` in the `openshift-gitops` namespace and restart the `multicluster-operators-application-*` pod in the `open-cluster-management` namespace.

https://issues.redhat.com/browse/ACM-23907

Version-Release number of selected component (if applicable):

latest-2.14

How reproducible:

Always

Steps to Reproduce:

1. Create a pull model applicationset (will encounter this issue)
2. Perform z stream upgrade.
3. Apply workaround listed above.
4. Notice that in the Application Page, the clusters field for each applicationset is None
5. Click into Application Details Page, the clusters field for applicationset is as expected

Actual results:

ApplicationSet clusters field is non on Application Page

Expected results:

ApplicationSet clusters field should be as expected

Additional info: