fix(javascript): expose sub algoliasearch client's type

[shortcuts]

🧭 What and Why

🎟 JIRA Ticket:

• https://algolia.atlassian.net/browse/APIC-590
• https://algolia.atlassian.net/browse/APIC-604

Changes included:

Sub algoliasearch client's type are not exposed, which can be useful in complex implementations like in the Crawler. It also help to differentiate which client does what.

🧪 Test

CI :D

[netlify]

✅ Deploy Preview for api-clients-automation ready!

Name	Link
🔨 Latest commit	ee4d93c
🔍 Latest deploy log	https://app.netlify.com/sites/api-clients-automation/deploys/62e0f6f7e75529000872c42d
😎 Deploy Preview	https://deploy-preview-873--api-clients-automation.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[algolia-bot]

✗ The generated branch has been deleted.

If the PR has been merged, you can check the generated code on the main branch.
You can still access the code generated on main via this commit.

[bodinsamuel]

I think we did it before it was published as multiple packages but it's no longer useful imo,
e.g: you can import SearchClient with @algolia/client-search instead of { SearchClient } from 'algoliasearch'
wdyt?

[shortcuts]

I think we did it before it was published as multiple packages but it's no longer useful imo, e.g: you can import SearchClient with @algolia/client-search instead of { SearchClient } from 'algoliasearch' wdyt?

Wouldn't typescript complain until you've added @algolia/client-search as a dependency if so? IIRC it was something people were complaining about

[shortcuts]

There was a bump on the open-issue for v4: algolia/algoliasearch-client-javascript#1080 (comment)

[bodinsamuel]

yeah okay for this issue I get it 👌🏻

[bodinsamuel]

I should forbid you to force-push 😬