feat(weaviate): Migrate to the new Weaviate client version 3

[my8bit]

As stated in the official documentation for the Weaviate TypeScript client they are deprecating the v2 version of the client.

The v3 client is the current TypeScript client. If you have code written for the v2 client, you should migrate it to v3.

The v2 client version is still available in npm, however you should not use it to begin new projects.

Source: Weaviate Documentation

This MR is implementing the necessary changes to be able to use the v3 of the client.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
langchainjs-docs	✅ Ready (Inspect)	Visit Preview		Jan 30, 2025 11:00am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
langchainjs-api-refs	⬜️ Ignored (Inspect)			Jan 30, 2025 11:00am

[hsm207]

@my8bit what else is needs to be implements to get this ready for review?

[my8bit]

Hey @hsm207, thanks for reaching out. There is a still usage of the old v2 client for compatibility.

From the functional perspective to keep the behavior as close as possible to v2:

• [ ] Enabled support of the filter option for delete method have to support the filter parameter
• [ ] Support to deletion of the tenant if specified and still applicable
• [ ] Enabled support of the filter option for similaritySearchVectorWithScoreAndEmbedding method
• [ ] Support of the tenant for similaritySearchVectorWithScoreAndEmbedding if specified and still applicable
• [ ] Correctly passing the distance and vector from search results to the final Document

[hsm207]

thanks @my8bit for clarifying. I'd like to try making a contribution. Can you add me and @malgamves to your fork so we can collab on this PR?

[my8bit]

hsm207

Thanks! I've sent invites with write access

[benjamincburns]

Apologies for missing this, but this has been changed in a different PR.