Fix problems with local libSQL DB

[Fryuni]

Changes

• Fixes problems related to using local files as libSQL remote reported on Discord with the sunsetting of Studio
• Relative paths were being treated as absolute paths and resulting on paths to folder that didn't exist or permission error trying to create a file on the filesystem root
• Pushing the schema to a new local file DB wasn't working. Pushing to remote server with a local file as embedded replica was.

Testing

• A new test for each of the problems was added

Docs

The new behavior matches the documentation

[changeset-bot]

🦋 Changeset detected

Latest commit: c5a5e52

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

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

[ematipico]

It's worth leaving a comment here and explaining the check. The comment should explain:

• why SQLITE_ERROR?
• why rawCode === 1?

[Fryuni]

Ok, I went to the source code to understand the error codes. It turns out the rawCode adds nothing here; it is just the numeric value of the enum while code is the name of the value. code: 'SQLITE_ERROR' will always come with rawCode: 1.

Also, SQLITE_ERROR is a generic error code used for multiple things. We'll have to check the message to ensure we only capture the error code we care about.

We'll still need to check for both codes because the library throws two errors when reading a non-existing table:

• Connected to a remote DB it throws with the code SQLITE_UNKNOWN and message SQLITE_UNKNOWN: SQLite error: no such table: some_table
• Connected to an in-memory or a local file DB it throws with the code SQLITE_ERROR and message SQLITE_ERROR: no such table: some_table

I'll change the code to properly reflect that.