[Store][Supabase] Add store

[junaidbinfarooq]

Q	A
Bug fix?	no
New feature?	yes
Docs?	yes
Issues	Fix #320
License	MIT

This PR adds support for Supabase as a vector store backend, leveraging Supabase's pgvector extension through the REST API.

Features

• Supabase Store Bridge: Full integration with Supabase's REST API and pgvector extension
• Bundle Configuration: Complete YAML configuration support for the AI Bundle
• Batch Operations: Efficient document insertion with chunking (200 docs per request)
• Vector Search: Similarity search with configurable match count and score thresholds
• Manual Setup: Clear documentation for required database schema setup

Key Differences from Postgres Store

Unlike the direct Postgres store, the Supabase bridge:

• Uses REST API instead of direct database connections
• Requires manual database setup (tables, functions, indexes)
• Supports Supabase's hosted PostgreSQL with pgvector

[OskarStark]

Following #604, please make the http client configurable, you can barely copy paste from #604, thanks

[junaidbinfarooq]

I do not see it done for any other store. Am I missing something here?

[OskarStark]

After a rebase you should

[junaidbinfarooq]

Done.

[OskarStark]

still sclaraNode()

[junaidbinfarooq]

I do not understand.
Could you help me here?

[OskarStark]

Sorry, sure, please use stringNode() or integerNode()

[junaidbinfarooq]

Addressed the review.
However, I'd like to mention that many of the comments I've seen in this and a few other PRs seem to be nitty-gritty IMO, and especially come at a later stage in the PR, unless there is a particular doc on coding standards in the said repo that I have missed so far.

[OskarStark]

We try to keep the code a little bit in sync. What coding standards do you mean?

[junaidbinfarooq]

We try to keep the code a little bit in sync. What coding standards do you mean?

Something like a contributing guide or PSR that specifically details the coding standards to be followed when contributing to the repo. This will ensure we have a consistent coding style throughout the codebase without having the maintainers worry much about it IMO.