Drop privileged SCC from RBAC grants

[gouthampacha]

Summary

• Remove the privileged SCC from kubebuilder RBAC markers, runtime policy rules, and generated ClusterRole/Role manifests
• The namespace-scoped Role that existed solely for the privileged SCC is eliminated
• Only the anyuid SCC remains, which is sufficient for all manila services

Follow-up to #597 which removed the privileged security context from the manila-share StatefulSet.

Jira: OSPRH-32347

Test plan

• make manifests regenerates config/rbac/role.yaml without privileged
• make generate succeeds
• CI functional tests pass
• grep -r 'privileged' internal/ config/rbac/ returns no SCC-related hits

🤖 Generated with Claude Code

[fmount]

/lgtm thanks a lot for this one!

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fmount, gouthampacha

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [fmount,gouthampacha]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[centosinfra-prod-github-app]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/rdoproject.org/buildset/d3eca927587549558be12769b5920c24

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 07m 44s
❌ manila-operator-kuttl FAILURE in 52m 37s
❌ manila-operator-tempest FAILURE in 1h 44m 55s

[fmount]

@gouthampacha the CI issue seems a real problem w/ manila-db-sync job that is not running. I think this is related to the fact we build the job with [1] and we should probably remove:

SeccompProfile: &corev1.SeccompProfile{
			Type: corev1.SeccompProfileTypeRuntimeDefault,
		},

that is incompatible w/ anyuid. I guess we had that because we used privileged, but we need to fix the securityContext as well if we remove the rbac entirely.

[1] https://github.com/openstack-k8s-operators/manila-operator/blob/main/internal/manila/funcs.go#L43

[fmount]

@gouthampacha retriggering CI with the updated SecurityContext (see my previous comment)