[ML] Decouple edit-anomaly-swimlane UI action

[darnautov]

Summary

• Decouples edit-anomaly-swimlane and apply-time-range-selection UI actions from embeddable framework

Part of #178375
Part of #174967

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[ThomThomson]

Action conversions LGTM! Code only review, but all of the conventions are followed very well. Great usage of the existing APIs, + creating new ones.

Left one very minor nit.

[ThomThomson]

This type is really clean and straightforward. Nice work!

This is not necessary, but interfaces have slightly better editor time performance than types, so we're starting to recommend using the interface syntax whenever possible. This could be rewritten like:

export interface AnomalyChartsEmbeddableApi extends HasType<AnomalyExplorerChartsEmbeddableType>, MlEmbeddableBaseApi, AnomalyChartsFieldSelectionApi {}

[darnautov]

Updated in 517e8a8

[peteharverson]

Tested latest changes and LGTM.

Is the 'Clear selection' action also covered here, or does that not need to be decoupled?

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 89cc3dc

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
ml	1949	1950	+1

Async chunks

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

id	before	after	diff
ml	3.7MB	3.7MB	+1.2KB

History

• 💔 Build #198797 failed 517e8a8
• 💚 Build #198738 succeeded 9ea9402
• 💚 Build #198715 succeeded f5b5414
• 💛 Build #198632 was flaky 77896c0
• 💔 Build #198568 failed ac4b184

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

cc @darnautov