Description of problem:

When attempting to use the RBAC UI to create a clusterpermission, after labeling the kubevirt roles with the correct label, rbac.open-cluster-management.io/filter=vm-clusterroles, the kubevirt roles wont show up in the UI still if the local-cluster name has been renamed to something else

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

How reproducible:

Steps to Reproduce:

1. enable fine-grained rbac preview to true under the spec.overrides.components in the mch cr instance
2. label the local-cluster custom name with environment=virtualization in the acm console under the infrastructure tab
3. navigate to the governance tab under acm console and find the policy-virt-clusterroles policy and enforce it
4. attempt to create a cluster permission in the rbac ui but no role will show up in the dropdown menu

Additional info:

due to leveraging search to find the cluster roles, the hardcoded value local-cluster is being used which means if the enviroment is using custom local-cluster name other than the default one being used, the kubevirt roles wont show up in the ui