Which issue does this PR close?

No one is using libsql to access data and it's lack of the maintainance.

At the same time: https://turso.tech/blog/introducing-limbo-a-complete-rewrite-of-sqlite-in-rust

The upstream is going to rewrite sqlite in rust by limbo.

2 years ago, we forked SQLite. We were huge fans of the embedded nature of SQLite, but longed for a more open model of development. libSQL was born as an Open Contribution project, and we invited the community to build it with us.

As a result, libSQL is an astounding success. With over 12k GitHub stars, 85 contributors, and features like native replication and vector search, libSQL is the engine that powers the Turso platform.

Today we are announcing a more ambitious experiment: what could we achieve, if we were to completely rewrite SQLite in a memory-safe language (Rust)? With the Limbo project, now available at github.com/tursodatabase/limbo, we are now trying to answer that question.

Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?