Add Qdrant vector database client

[Zhaoziyuan2024]

/claim #273

Summary

• add a REST-backed Qdrant client for the JS vector-db package without using Qdrant SDK packages
• export Qdrant alongside the existing Supabase vector database integration
• support collection create/read/delete, point upsert/insert, query/search, retrieve by id, and delete by id
• cover the Qdrant REST paths and payloads with offline Jest tests
• declare dotenv because the vector-db package imports it during build

Verification

• pnpm exec jest src/vector-db/src/tests --runInBand
• pnpm exec tsc -b

Demo

• The included Jest suite mocks the HTTP client and verifies the exact Qdrant REST requests for create/upsert/query/search/get/delete without requiring a live Qdrant service.

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[Zhaoziyuan2024]

I have read the Arakoo CLA Document and I hereby sign the CLA

[Zhaoziyuan2024]

recheck

[Zhaoziyuan2024]

I noticed the CLA workflow appears to check a different issue-comment trigger phrase than the one the bot asks contributors to post.

In .github/workflows/cla.yml, the step only runs for issue comments matching:

I have read the CLA Document and I hereby sign the CLA

But the configured custom-pr-sign-comment and the bot prompt ask for:

I have read the Arakoo CLA Document and I hereby sign the CLA

That requested signature comment has already been posted, followed by recheck, but the CLA run still reports the PR committer as unsigned. Could a maintainer please advise whether the older trigger phrase should be used as well, or update/re-run the CLA workflow condition so it recognizes the configured Arakoo CLA phrase?

[Zhaoziyuan2024]

recheck

[Zhaoziyuan2024]

Ready for review/reward for bounty #273.

/claim #273 is already in the PR body. CLA is signed and the JS/changes checks are green.

Scope covered:

• dependency-free REST-backed Qdrant client for the JS vector-db package
• export Qdrant alongside the existing vector database integration
• create/get/delete collection, upsert/insert points, query/search, retrieve by id, and delete by id
• offline Jest coverage for the exact Qdrant REST request shapes, without needing a live Qdrant service

Validation performed:

• pnpm exec jest src/vector-db/src/tests --runInBand
• pnpm exec tsc -b