[ML] Anomaly Detection alert initialisation from the ML app

[darnautov]

Summary

Part of #88940

• Allows initializing the Anomaly Detection alert directly in the Job wizard
  

• Allows initializing the Anomaly Detection alert from the Job list with single and bulk actions
  

• Adds "Create alert" action to the jobs management table
  
  

• Adds control for including/excluding interim results
  

• Removes Watcher integration from the ML plugin

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)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[jgowdyelastic]

Code LGTM

[spong]

Just to clarify, is there any expectation we check this permission and restrict access within Detections for creating ML Rules? I imagine no since the Detection Engine is managed as a separate application, and this seems specific to the new ML Alert Type, but want to make sure we're respecting permissions as expected from the ML permissions model perspective.

i.e Should we disable the ML Detections Rule type if canCreateMlAlerts:false?

[darnautov]

hey @spong! 👋 I reckon canCreateMlAlerts should not affect the ML Detections Rule in Security app, as it's dedicated to the ML related alert types only. No actions are required on your side

[spong]

Security Solution changes LGTM! One outstanding question on if we should be respecting the new canCreateMlAlerts ML permission within the Detection Engine, but we can open a dedicated issue to address if necessary. Thanks @darnautov! 🙂

[peteharverson]

Tested and LGTM

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: a0503e0

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
ml	1735	1730	-5

Async chunks

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

id	before	after	diff
ml	6.3MB	6.3MB	-22.4KB
securitySolution	7.5MB	7.5MB	+24.0B
total			-22.4KB

Page load bundle

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

id	before	after	diff
ml	68.2KB	68.1KB	-120.0B

History

• 💔 Build #106634 failed 8fa5d84
• 💚 Build #106615 succeeded b37d7de
• 💔 Build #106585 failed 4f366ba
• 💔 Build #106572 failed 876c908
• 💔 Build #106534 failed 898c87d

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

[kibanamachine]

Backport result

{"level":"info","message":"POST https://api.github.com/graphql (status: 200)"}
{"level":"info","message":"POST https://api.github.com/graphql (status: 200)"}
{"meta":{"labels":[":ml","Feature:Alerting","Feature:Anomaly Detection","auto-backport","release_note:enhancement","v7.12.0","v8.0.0"],"branchLabelMapping":{"^v8.0.0$":"master","^v7.12.0$":"7.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"},"existingTargetPullRequests":[]},"level":"info","message":"Inputs when calculating target branches:"}
{"meta":["7.x"],"level":"info","message":"Target branches inferred from labels:"}
{"meta":{"killed":false,"code":2,"signal":null,"cmd":"git remote rm kibanamachine","stdout":"","stderr":"error: No such remote: 'kibanamachine'\n"},"level":"info","message":"exec error 'git remote rm kibanamachine':"}
{"meta":{"killed":false,"code":2,"signal":null,"cmd":"git remote rm elastic","stdout":"","stderr":"error: No such remote: 'elastic'\n"},"level":"info","message":"exec error 'git remote rm elastic':"}
{"level":"info","message":"Backporting [{\"sourceBranch\":\"master\",\"targetBranchesFromLabels\":[\"7.x\"],\"sha\":\"a8e1e47de6ee7b385c17928e91589db630835d6c\",\"formattedMessage\":\"[ML] Anomaly Detection alert initialisation from the ML app  (#91283)\",\"originalMessage\":\"[ML] Anomaly Detection alert initialisation from the ML app  (#91283)\",\"pullNumber\":91283,\"existingTargetPullRequests\":[]}] to 7.x"}

Backporting to 7.x:
{"level":"info","message":"Backporting via filesystem"}
{"level":"info","message":"Creating PR with title: \"[7.x] [ML] Anomaly Detection alert initialisation from the ML app  (#91283)\". kibanamachine:backport/7.x/pr-91283 -> 7.x"}
{"level":"info","message":"POST /repos/elastic/kibana/pulls - 201 in 1172ms"}
{"level":"info","message":"Adding assignees to #91441: darnautov"}
{"level":"info","message":"POST /repos/elastic/kibana/issues/91441/assignees - 201 in 526ms"}
{"level":"info","message":"Adding labels: backport"}
{"level":"info","message":"POST /repos/elastic/kibana/issues/91441/labels - 200 in 365ms"}
View pull request: https://github.com/elastic/kibana/pull/91441