[Semantic Text UI] Adapt inference endpoint calls to new API spec

[saikatsarkar056]

The inference endpoint API spec has changed. Now, we need to refer to 'endpoints' property instead of the 'models' property while gathering the inference_endpoints informations using _inference/_all

[saikatsarkar056]

We already have several tests that cover the usage of inference_models received from _inference/_all. Should we add additional tests specifically for register_get_route?

[sabarasaba]

Changes lgtm, didn't test locally. I was wondering though if we should add a test to make sure we catch potential ES api changes like this one that would break in kibana.

[sabarasaba]

Should we add additional tests specifically for register_get_route?

I saw this comment after I left the review, I think it would be a good idea to include some here for sure

[saarikabhasi]

LGTM. Tested locally. New inference endpoint that are created from inference flyout are shown in the select inference endpoint dropdown
++ on adding additional tests as well.

[sphilipse]

Yup. Specifically we should have FTR tests that test these endpoints in isolation, as well as FTR tests that run through the UI. And ideally we should have them for both stateful and Serverless.

[saikatsarkar056]

Yup. Specifically we should have FTR tests that test these endpoints in isolation, as well as FTR tests that run through the UI. And ideally we should have them for both stateful and Serverless.

@sphilipse I added some FTR tests for the endpoint. I will the FTR tests that run through the UI in a separate PR. Thank you.

[walterra]

ML related changes LGTM.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 534e9b1

Metrics [docs]

✅ unchanged

History

• 💛 Build #210352 was flaky d0e9e2f
• 💔 Build #210341 failed dc7b41f
• 💚 Build #209645 succeeded 6857738

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

cc @saikatsarkar056