Use apsw instead of sqlite

[pydanny]

Replaces the built-in Python binding with the apsw library

Notes about the migration / Future PRs

1. To minimize changes and make reviewing easier, we import apsw as sqlite3 and set OperationError to apsw.Error. In a soon-to-be-submitted PR we will change sqlite3 to apsw
2. In a series of future PRs we will begin to move from the generic OperationError (shim of apsw.Error) to more precise errors
3. Transformations can be improved/expanded https://www.sqlite.org/lang_altertable.html#making_other_kinds_of_table_schema_changes
4. This doesn't remove the remainder of rowid, that will happen in another PR

Reasons:

• Improved performance on Python 3.12: Internal tests show it can handle ~100-200x more concurrent reads than sqlite3 without configuration
• Easier to config
• Better stack traces
• More precise errors, including built-in support for Busy Handling

Source AnswerDotAI/sqlite-minutils#44

Tests

• pytests (see tests directory)
• Fastlite: sqlite3 => apsw fastlite#47
• Fasthtml notebooks
• adv_app
• solveit

[pydanny]

@audreyfeldroy and I review this PR together: https://drive.google.com/file/d/1W7CLwcKNZOand7YfK4iDDjNTPHqKPRUR/view?usp=drive_link

[jph00]

Exciting!