[Infra Monitoring]: add rac to feature privileges for logs and metrics

[mgiota]

Fixes #130761

Notes for the reviewer

• The user would get a Forbidden error when they had the option to Update the workflow_status in the Alerts Page https://github.com/elastic/sdh-kibana/issues/2798.
• Current fix has already been applied [7.17] [Observability] [RAC] [Alerts] Resolve bug where "mark as.." for a single alert would redirect to security solution route #130609 in 7.17.4
• Since worflow_status filtering and Mark as acknowledged and Mark as closed options have been removed from the alerts view in 8.0 [8.0][RAC] 117686 replace alert workflow status in alerts view #118723, you won't be able to reproduce the bug on main, but still rac privileges need to be present to avoid any future privilege related bugs

Question

Shall we backport this fix to releases previous to 7.17.4 as well?
Update: Based on #111296, RAC feature flags were disabled by default for 7.15 and 7.16, so I would say we don't need to backport at all?

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 90053be
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

✅ unchanged

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @mgiota

[matschaffer]

Seems reasonable to me. Should we add something similar to https://github.com/elastic/kibana/blob/main/x-pack/plugins/monitoring/server/plugin.ts#L269 ? I don't see an api privilege there today, so not sure.

[mgiota]

Should we add something similar to https://github.com/elastic/kibana/blob/main/x-pack/plugins/monitoring/server/plugin.ts#L269 ?

@matschaffer Good point! I don't think we need to do something to this file at the moment, since stack monitoring rule types are not RAC registered yet as far as I know. But something we should definitely need to keep in mind, when we port stack monitoring rule types to alerts as data indices!