RBAC configuration in the Feast operator

[dmartinol]

Is your feature request related to a problem? Please describe.
Feast services currently support RBAC configuration via the feature_store.yaml, which is managed by the Feast Operator in Kubernetes environments. To enable proper authorization setup by feature store administrators, the Feast Operator should also provide capabilities to define and enforce consistent RBAC settings across all services.
Additionally, sensitive information such as IDP server credentials should be protected using encoded secrets within the deployment namespace.

This issue relates to #4561.

Describe the solution you'd like
Authorization settings must be given in the FeatureStore custom resource and be propagated by the operator to the deployed Feast services.

Describe alternatives you've considered
Since the operator reconciles all changes to the deployed applications to match the latest state of the FeatureStore resource, there are no alternatives that we could consider in order to inject the authorization settings, located in the feature_store.yaml, into the Feast services.

Additional context

• RBAC definitions in Feast
• Feast authorization settings

[dmartinol]

Related PRs:

• feat: RBAC Authorization in Feast Operator #4786
• feat: OIDC authorization in Feast Operator #4801