Replace SQLite with Turso

[antimora]

Feature description

Replace SQLite with @tursodatabase/turso where SQLite is currently used in the project.

Feature motivation

Using Turso could improve portability and simplify working with a remote-first SQLite-compatible database offering. If the current SQLite usage is creating limitations around deployment, synchronization, or scaling, adopting Turso may provide a more flexible path forward while keeping a SQLite-oriented model.

(Optional) Suggest a Solution

• Audit where SQLite is currently used in the codebase, build, tests, and documentation.
• Evaluate whether the intended replacement is the Turso platform itself, the libSQL/Turso client stack, or another integration layer that is compatible with the project architecture.
• Introduce the new database dependency and adapt the persistence layer behind a narrow abstraction to minimize downstream changes.
• Update configuration, environment variables, and local development workflows.
• Migrate tests and CI setup away from SQLite-specific assumptions.
• Document the migration path, compatibility expectations, and any operational tradeoffs.

Potential considerations:

• Whether full SQLite compatibility is required for all existing behaviors.
• Impact on offline or local-only workflows.
• Dependency, licensing, and runtime implications for Rust targets supported by Burn.

[nathanielsimard]

@Marc-AnthonyG @jwric will be happy!

[Marc-AnthonyG]

I doubt we would have any difficulty with compatibility. We would have to use some really strange corner of SQLite to face incompatibility in the migration. Anyway, I know one of maintainer of Turso so If you encounter any difficulty we can check with him to fix upstream in turso directly. (: