[ResponseOps] add snoozing MVP implementation to alerting framework

[pmuellr]

Summary

resolves #126512

This PR fills in some of the missing pieces with the new rule
snoozing functionality described in meta issue
#125804

The main bit is the calculation of whether a rule is "snoozed". Prior
to this, we only had the mute_all boolean property, but now we also
have a snooze_end_time Date | null property. Here's how they work:

	snooze_end_time: null	snooze_end_time: date
mute_all: true	rule is snoozed forever	invalid
mute_all: false	rule is not snoozed	rule is snoozed till date

This is handled in the function isRuleSnoozed() in
x-pack/plugins/alerting/server/task_runner/task_runner.ts

Summarize your PR. If it involves visual changes include a screenshot or gif.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: cf74055
• Interpreting CI Failures
• Storybooks Preview
• Cloud Deployment
• Webpack Bundle Analyzer

Failed CI Steps

• Default CI Group #12
• Default CI Group #12
• Default CI Group #17
• Default CI Group #17
• Jest Integration Tests #2
• Checks

Test Failures

• [job] [logs] Default CI Group #17 / alerting api integration security and spaces enabled Alerts alerts update superuser at space1 should handle update alert request appropriately
• [job] [logs] Default CI Group #17 / alerting api integration security and spaces enabled Alerts alerts update superuser at space1 should handle update alert request appropriately
• [job] [logs] Default CI Group #12 / alerting api integration spaces only Alerting get public should handle get alert request appropriately
• [job] [logs] Default CI Group #12 / alerting api integration spaces only Alerting get public should handle get alert request appropriately
• [job] [logs] Jest Integration Tests #2 / migration actions reindex & waitForReindexTask resolves left wait_for_task_completion_timeout when the task does not finish within the timeout
• [job] [logs] Jest Integration Tests #2 / migration actions waitForPickupUpdatedMappingsTask resolves left wait_for_task_completion_timeout when the task does not complete within the timeout

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
alerting	298	299	+1

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
alerting	38.0KB	38.1KB	+51.0B

Unknown metric groups

API count

id	before	after	diff
alerting	306	307	+1

ESLint disabled in files

id	before	after	diff
apm	15	14	-1
securitySolution	67	66	-1
uptime	7	6	-1
total			-3

ESLint disabled line counts

id	before	after	diff
apm	85	82	-3
uptime	48	42	-6
total			-9

References to deprecated APIs

id	before	after	diff
fleet	5	4	-1
monitoring	40	28	-12
stackAlerts	183	157	-26
upgradeAssistant	8	3	-5
total			-44

Total ESLint disabled count

id	before	after	diff
apm	100	96	-4
securitySolution	514	513	-1
uptime	55	48	-7
total			-12

History

• 💔 Build #29649 failed 882a72b
• 💔 Build #29556 failed df6075d
• 💔 Build #29229 failed 2530283
• 💔 Build #29124 failed 0ca9389

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

[pmuellr]

closing in favor of #127694