Added refreshSchema()

[Chriztiaan]

Updating the schema can causing queries and watch calls to become stale as they would use outdated source tables from a previous version of the schema. This PR adds the ability to explicitly update the version of the schema used for existing queries and watch calls.

[rkistner]

The build checks are failing due to not supporting the lastest drift version. It's safe to increase the pana score threshold for now, until we properly fix the compatibility version later.

[Chriztiaan]

@rkistner @stevensJourney I have removed the exclusiveLock implementation for the moment. If there are concerns in the powersync package, we can instead depend on a lock there.

This version of the PR looks much cleaner than the first iteration so I am happy about it.
Just not 100% sure about putting the default refreshSchema implementation in the SqliteQueries mixin.

[Chriztiaan]

@rkistner @stevensJourney I have removed the exclusiveLock implementation for the moment. If there are concerns in the powersync package, we can instead depend on a lock there.

This version of the PR looks much cleaner than the first iteration so I am happy about it. Just not 100% sure about putting the default refreshSchema implementation in the SqliteQueries mixin.

I realised with this implementation, I don't have access to refreshSchema in transactions - which would be nice as it would allow us to pair an updateSchema and refreshSchema inside a lock/transaction in the PowerSync package.

[rkistner]

I realised with this implementation, I don't have access to refreshSchema in transactions - which would be nice as it would allow us to pair an updateSchema and refreshSchema inside a lock/transaction in the PowerSync package.

I think that's expected. Transactions can't span multiple connections, so there is no way to refresh the schema across connections in one transaction. And if you specifically want that command within a transaction, you can just call the PRAGMA statement directly.