[ML] Fixes import and improves validation for Anomaly Detection and Data Frame Analytics jobs

[KodeRad]

Summary

Fixes: #239574

This PR:

• Fixes the issue where it was impossible to import the job that was exported based on data view that used more than one index.
• Adds Datafeed validation for Anomaly Detection jobs. It is displayed as warnings. Even if there are missing indices or other warnings it is possible for the user to import the jobs. These warnings might be then addressed by for example adding missing indices.
• Add Source index validation via esSearch call. This checks if Data Frame Analytics job can be imported. They can not be imported if the source index is missing.

Screenshots:

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

• 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
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
• Flaky Test Runner was used on any tests changed
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
• Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

• See some risk examples
• ...

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 9aab8c1

Failed CI Steps

• FTR Configs #47

Test Failures

• [job] [logs] FTR Configs #47 / Entity Analytics - Privilege Monitoring @ess @serverless @skipInServerlessMKI Entity Privilege Monitoring Engine Integrations Sync integrations sync should update and create users within lastProcessedMarker range during update detection

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
ml	5.4MB	5.4MB	+3.3KB

History

• 💔 Build #363310 failed 1415d9c

cc @KodeRad

[jgowdyelastic]

Left a couple of comments, but otherwise LGTM

[peteharverson]

Tested, using the use case in the original issue, and LGTM.

[kibanamachine]

Starting backport for target branches: 8.19, 9.0, 9.1, 9.2

https://github.com/elastic/kibana/actions/runs/19577168073

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.19	Backport failed because of merge conflicts
❌	9.0	Backport failed because of merge conflicts
❌	9.1	Backport failed because of merge conflicts
❌	9.2	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 242263

Questions ?

Please refer to the Backport tool documentation

[KodeRad]

💚 All backports created successfully

Status	Branch	Result
✅	9.2
✅	9.1
✅	9.0
✅	8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation