Investigate removing the dependency on Query DB Collection

[ivasilov]

What to build

Investigate whether the Supabase collection adapter should continue depending on @tanstack/query-db-collection, wrap it more narrowly, or replace it with a direct TanStack DB collection implementation.

The current dependency provides a useful bridge between TanStack Query and TanStack DB, but it may also constrain Supabase-specific behavior such as Realtime subscription lifecycle, PostgREST pagination, optimistic writes, rollback, and future offline support. This issue should evaluate whether the dependency is still the right foundation as the adapter matures.

The outcome should be a design recommendation, not a large refactor by default. If removal is recommended, document the smallest safe migration path, expected public API changes, test coverage needed, and whether users should observe any behavior changes.

Acceptance criteria

• Explain what @tanstack/query-db-collection provides to this adapter today.
• Identify the Supabase-specific behaviors it helps or constrains.
• Compare keeping it, wrapping it, and replacing it with a direct adapter.
• Recommend a path forward with tradeoffs.
• If removal is recommended, outline a safe follow-up implementation plan.

Blocked by

None - can start immediately.