fix: auto-migrate after DB restore and force re-login

- After importing a backup, run prisma migrate deploy so any schema
  migrations the backup is missing are applied automatically. This
  prevents pages from failing due to missing tables/columns when the
  backup was taken on an older version of the app.
- Force logout and redirect to login after a successful restore so the
  JWT is refreshed against the restored database (prevents userId
  mismatch causing user-scoped queries to return empty results).
- Fix getTotalPatientCount() in /status route to pass userId so it
  counts only the current user's patients instead of all patients.
- Add prisma.$connect() after $disconnect() to ensure a clean reconnect.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

packages/db/generated/prisma/package.json

@@ -1,5 +1,5 @@
 {
-  "name": "prisma-client-763f714d62d731c0b365e1acdf19cac05ed4e6562d30b17cc8ffd11e6278eb14",
+  "name": "prisma-client-739d12442b0153003c2c61c3294d05ecee806c9039d5ecd310b332b3c1eca2ec",
   "main": "index.js",
   "types": "index.d.ts",
   "browser": "default.js",