S3 to Turso database

[brollin]

Closes #290 and closes #294. Ultimately this PR accomplishes:

• switch backend endpoints from using s3 to using turso as a data store (except beat map stuff, which needs a rework anyways)
• nail down a final database schema with drizzle orm
• setup means to switch between local (local sqlite file) and production database (turso hosted database)
• some inconsequential random bugfixes

Still to do in a followup:

• remove now irrelevant code related to s3 stuff (in particular stuff in the scripts and utils directories)
• document all the things and update ONSITE_SETUP.md
• set up a regular backup somehow (we can just dump the db into s3)