Use androidx sqlite bindings internally

[simolus3]

This restructures our internal driver implementations to be aligned with cross-platform APIs from the androidx.sqlite:sqlite library, and removes all internal usages of SQLiter and SQLDelight:

• The :persistence project has been removed.
• The :dialect project has been removed.

As a replacement, I've introduced the internal :drivers:common project which adds a common interface for raw SQLite connections and statements. It re-uses the androidx.sqlite definitions, but adds a driver that allows adding update and commit hooks (for which androidx.sqlite has no API yet)). On native platforms, I'm using the androidx.sqlite:sqlite-framework implementation. On the JVM, I've moved the sqlite-jdbc implementation from :core to :drivers:common.

In :core, the public interfaces like the cursor are then consistently implemented across the common underlying SQLiteConnection API.

I've also added a new API to PowerSyncDatabase to give out a temporary view to an underlying SQLiteConnection. This would give users full control over the statements to run, while still letting the PowerSync SDK taking care of connection management.

This is only a first step, but I hope that it makes it easier to introduce more features in the future, such as:

1. Splitting :drivers:common into :drivers:sqlite3 and :drivers:sqlcipher, and then letting users swap out driver implementations if they want an encrypted database.
2. Allowing the use of custom driver implementations, which could allow the SDK to e.g. share a connection pool with GRDB in the future.
3. Supporting custom database paths on all platforms.
4. Supporting otherr SQLite toolkits like Room or SQLDelight.

TODOs:

• Check Swift SDK still works with this.
• Check we're using the same paths as SQLiter by default