fix: Drizzle Read Connection Concurrency

[stevensJourney]

Overview

should close #763

The current Drizzle driver uses the AbstractPowerSyncDatabase writeLock method for most query operations. Read locks are only used if an explicit read only transaction is started.

Using a write lock for Select queries hampers concurrency in applications using environments which support multiple read connections - such as React Native and Node.js. Thanks @rkistner for adding this!

This PR updates the query execution logic to use queryMetaData from drizzle-team/drizzle-orm#4447 in order to detect SELECT queries. This approach has some limitations:

• queryMetaData is not available for db.query[collectionName] queries. We use a slightly nasty override for db.query[collectionName] queries. The current version only has findMany and firstFirst options - which should be read queries

[changeset-bot]

🦋 Changeset detected

Latest commit: 7e4810d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@powersync/drizzle-driver	Minor
@powersync/node	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[stevensJourney]

The Test Packages action is still super flaky. I've seen the Node.JS sync tests fail almost 15 times :(. Skipping this for now in order to get this out.