[Logs UI] Migrate to the new space-aware ML APIs

[weltenwort]

Summary

When the ML plugin migrates to new, space-aware Kibana APIs (#64172), the parts of the Logs UI that integrate with ML will have to adapt.

The readiness of this effort is contingent on the availability of the new APIs:

• [Logs UI] [ML] Use ML's mlAnomalySearch for all searches on the anomaly index  #67861

[elasticmachine]

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

[jasonrhodes]

@weltenwort can we list out what still needs to be done to make this adaptation process complete? My understanding is we don't need to do anything, but that we can back out our own Space management (via Job ID) as long as we figure out how to be backwards-compatible. Is that the gist of it or is there more to it than that?

[weltenwort]

It depends a bit on how the Kibana-side ML APIs will change as part of this.

But from what I currently know about that, I agree that most of the changes will be related to the space id encoded in the job name. Ideally there will be an automatic migration by the ML plugin, which parses the space id out of the job id and assigns it to the correct space. That would remove the need for maintaining additional backwards-compatible code paths. We'd only have to adjust how the getJobId function derives the expected job ids on our side (i.e. remove the spaceId parameter).

[weltenwort]

Done by way of #68905, #77916 and #83127.