Connectors list: hide inference connector if inference endpoint does not exist

[alvarezmelissa87]

Summary

This PR adds a check to see if the inference endpoint exists before displaying inference connectors in the Connectors list.

This means that the default Elastic LLM connector (which is currently shown and just doesn't work) will now be hidden for users it is not enabled for.

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

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]

Pinging @elastic/ml-ui (:ml)

[alvarezmelissa87]

Due to the time sensitive nature of this change, I did not update types as I wanted to keep code churn to a minimum. I can create a follow up to get rid of this ignore.

[YulNaumenko]

I think it will be better to filter on the server side instead of the client making http calls for each .inference connector.

[dgieselaar]

it 100% should be on the server, otherwise there's too many places where this can be used and it's A) a lot of work to find/update them all, B) we risk missing something

[dgieselaar]

Also I agree with Yuliia, making this a blocking HTTP call per connector is not the right choice (at all).

[cnasikas]

+1 on this.

[darnautov]

PR with the server-side fix is up #217641

[alvarezmelissa87]

@elasticmachine merge upstream

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: a7dfdcb

Failed CI Steps

• Check Types

History

• 💔 Build #291321 failed 00d947e

cc @alvarezmelissa87

[alvarezmelissa87]

Created a duplicate inference endpoint check function to avoid circular dependency errors. This is a temporary fix due to time constraints of trying to get this in to fix the release blocker

[alvarezmelissa87]

Closing this in lieu of #217641