[Cloud Security] Handle Detection Rules and Benchmark rules errors

[opauloh]

Summary

This PR addresses the following:

• Handling errors when creating Detection rules
• Handling errors when muting/unmuting Benchmark rules
• Handling Alerts pending on loading state when the user doesn't have read permission to the Detection Rules alerts index (.alerts-security.alerts-default).
• Centralized benchmark rules mutation success/error logic in the useChangeCspRuleState hook.
• Fixed benchmark mute API that was disabling only one detection rule per benchmark rule.

Recordings

Read Only User (Without .alerts-security.alerts-default read permission)

Screen.Recording.2024-08-22.at.6.21.30.PM.mov

Read Only User (With .alerts-security.alerts-default read permission)

Screen.Recording.2024-08-22.at.6.44.11.PM.mov

Write permission user

Screen.Recording.2024-08-22.at.6.38.11.PM.mov

[elasticmachine]

Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security)

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: c275579

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
cloudSecurityPosture	480.3KB	480.5KB	+225.0B

History

• 💔 Build #229345 failed c3637f6
• 💔 Build #229338 failed 8a3b886

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