The idea/intention here is to remove the hardcoded roles on the UI side
https://github.com/Ginxo/console/blob/21b35f76db542d5685f96ca93fcfe28d2181ee8a/frontend/src/routes/AccessControlManagement/AccessControlManagementForm.tsx#L44
And to load roles (check https://github.com/stolostron/console/blob/0eb97f6f96445bb2e762ba72d11650d560b94bc5/frontend/src/routes/Infrastructure/Clusters/ClusterSets/ClusterSetDetails/ClusterSetAccessManagement/ClusterSetAccessManagement.tsx#L320 for loading them) and to filter them out by "rbac.open-cluster-management.io/filter" string as we agreed on https://redhat-internal.slack.com/archives/C08N0NBMM2S/p1747815085320159?thread_ts=1747078461.056459&cid=C08N0NBMM2S

The task is also about to clarify how to add "rbac.open-cluster-management.io/filter" label to kubevirt.io:view, kubevirt.io:edit, kubevirt.io:admin roles by default as it was done for default verbs applied for ClusterPermissions resource at https://github.com/stolostron/backplane-operator/pull/1507 This way, when both things are done, we will be able to see "kubevirt.io:view, kubevirt.io:edit, kubevirt.io:admin" on edit or create screens