[ResponseOps][FE] Alert creation delay based on user definition

[doakalexi]

Resolves #173009

Summary

Adds a new input for the user to define the notificationDelay. This input is available for life-cycled alerts (stack and o11y) rule types.

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
• Unit or functional tests were updated or added to match the most common scenarios

To verify

• Using the UI create a rule with the notificationDelay field set.
• Verify that the field is saved properly and that you can edit the notificationDelay
• Verify that you can add the notification delay to existing rules. Create a rule in a different branch and switch to this one. Edit the rule and set the notificationDelay. Verify that the rule saves and works as expected.

[doakalexi]

/ci

[doakalexi]

/ci

[doakalexi]

/ci

[doakalexi]

@lcawl and @mdefazio could you take a look at the ui and copy changes when you have a chance pls
I think the label and help text in the tooltip could be better.

[elasticmachine]

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

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 3058513

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
triggersActionsUi	1.4MB	1.4MB	+1.8KB

Page load bundle

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

id	before	after	diff
triggersActionsUi	106.2KB	106.3KB	+51.0B

Unknown metric groups

References to deprecated APIs

id	before	after	diff
triggersActionsUi	50	51	+1

History

• 💛 Build #188313 was flaky 324b151
• 💔 Build #188288 failed 95ddef5

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