Stack Rules Bulk enable/disable options are overly restricted

[EricDavisX]

Kibana version: 8.6.0-snapshot, kibana commit: 3f62042, issue is the same in 8.5.0 GA

Original install method (e.g. download page, yum, from source, etc.):
Tested on cloud-deploy to staging

Describe the bug:
When you are bulk selecting Stack Rules, the enable / disable options are overly restrictive as to what is shown to the user - if you have a mixed-cases of some rules that are enabled and some that are disabled, it only allows you to disable them. why not let users enable them in this case too?

Steps to reproduce:

1. create a bunch of stack rules
2. in Rules page enable at least 1 but not all of them
3. then select the current page set of rules and try to Enable them - it is not available in the list
   This will likely be more impactful or seen as oddly or inappropriately restrictive UX in light of coming bulk enable/disable rules work with 'select all' at play.

Expected behavior:
User can enabled a mixed-status set of rules, and disable them as well - regardless of state.

Screenshots (if relevant):

Showing that there is some logic in place here, if you only have selected 'Disabled' rules, then the 'Enable' option certainly shows in the UI and works:

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[mdefazio]

Thanks for bringing this up @EricDavisX .

Here's a proposed update to the UI:

Summary of edits:

• Popover buttons should be consistent with the Row action popover (EuiContextMenu)
• Segment snooze, other actions and delete into 3 sections in the popover
• If we're using the context menu, then 'snooze now' can be similar to how its done for the row actions (as a second panel)
• I'm good with the modal for schedule snooze actions. just a small edit on the button placement and button labels.

This bulk action component needs some more guidelines to be sure, as it's used a bit randomly. That said, the 'Select all x rules' option shouldn't be shown unless the user selects all items on the page. Not as necessary as the others, but we might as well try and determine the best practices for this component.

[guskovaue]

Was done in this PR: #145928