feat: use neon for managed postgres in production

I will use Neon for simplicity until I switch to a local client-side
IndexedDB or SQLite solution. Neon is what Vercel Postgres is. I figured
I would use Neon directly.

Ref: https://vercel.com/docs/storage/vercel-postgres#neon-partnership
Ref: https://orm.drizzle.team/docs/get-started/neon-new

svelte-ui/package.json

@@ -44,6 +44,7 @@
     "vitest": "^2.0.4"
   },
   "dependencies": {
+    "@neondatabase/serverless": "^0.10.3",
     "@supabase/sql-formatter": "^4.0.3",
     "@tailwindcss/forms": "^0.5.9",
     "@tailwindcss/typography": "^0.5.15",

svelte-ui/src/lib/server/db/index.ts

@@ -1,15 +1,15 @@
-import { drizzle } from "drizzle-orm/node-postgres"
+import { drizzle as postgres } from "drizzle-orm/node-postgres"
+import { drizzle as neon } from "drizzle-orm/neon-http"
 import { env } from "$env/dynamic/private"
 
 import * as tables from "./schema/tables"
 import * as relations from "./schema/relations"
 
-const schema = { ...tables, ...relations }
-
 if (!env.DATABASE_URL) throw new Error("DATABASE_URL is not set")
 
-export const db = drizzle({
-  schema,
-  logger: true,
-  connection: env.DATABASE_URL,
-})
+const schema = { ...tables, ...relations }
+const config = { schema, logger: true, connection: env.DATABASE_URL }
+
+export const db = env.DATABASE_URL.includes("neon")
+  ? neon(config)
+  : postgres(config)