feat(chat): add compatibility with algolia mcp search tool [DASH-2294]

[kombucha]

Summary

Fixes DASH-2294
Adds compatibility with the Algolia MCP Server search tool.

The MCP Server names search tools with a suffix (e.g., algolia_search_index_indexName) instead of just algolia_search_index. This PR adds a shim that falls back to the algolia_search_index tool implementation when encountering these suffixed tool names.

Result

By default, the chat widget now works with both:

• Standard algolia_search_index tool calls
• MCP Server style algolia_search_index_* tool calls

Testing

• Added a couple of unit tests ✅
• Tested manually by pointing one of the examples to a locally running instance

yarn --cwd examples/js/default-theme start

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 80970da:

Sandbox	Source
example-instantsearch-getting-started	Configuration
example-react-instantsearch-getting-started	Configuration
example-react-instantsearch-next-app-dir-example	Configuration
example-react-instantsearch-next-routing-example	Configuration
example-vue-instantsearch-getting-started	Configuration

[Haroenv]

you can update the bundlesize for InstantSearch.js development to give it more margin.

Just wondering why the patch happens both in the connector and the InstantSearch.js widget (but not react), isn't one of those redundant?

I think it also could be interesting to add a test to the common test suite (tests/common/widgets/chat)

[Haroenv]

we did the shim in the InstantSearch.js widget, but not the React InstantSearch widget, is that on purpose?

[kombucha]

It should be handled for the react flavour too.
The tools config is passed down through a few layers of component and is finally handled in packages/instantsearch-ui-components/src/components/chat/ChatMessage.tsx which I updated 👍

[Haroenv]

makes sense! This probably changes with #6874 that's just for @shaejaz to take in account

[shaejaz]

I think this would remain the same since you still need to map a tool into one with a layoutComponent in the js chat widget (and not in react) for it to be consumable in ui-components.

I'll try to see if this can be avoided in my PR tho.

[shaejaz]

lgtm! we do most of the chat unit testing in the common test suite, but this is good for now; can be added there later.

[shaejaz]

I think this would remain the same since you still need to map a tool into one with a layoutComponent in the js chat widget (and not in react) for it to be consumable in ui-components.

I'll try to see if this can be avoided in my PR tho.