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/shared/schemas/results/UserAggregateResult.schema.ts

@@ -11,7 +11,6 @@ export const UserAggregateResultSchema = z.object({  _count: z.object({
     npiProviders: z.number(),
     claims: z.number(),
     insuranceCredentials: z.number(),
-    shoppingVendors: z.number(),
     updatedPayments: z.number(),
     backups: z.number(),
     backupDestinations: z.number(),
@@ -23,9 +22,7 @@ export const UserAggregateResultSchema = z.object({  _count: z.object({
     aiSettings: z.number(),
     officeHours: z.number(),
     officeContact: z.number(),
-    procedureTimeslot: z.number(),
-    insuranceContacts: z.number(),
-    patientConversations: z.number()
+    procedureTimeslot: z.number()
   }).optional(),
   _sum: z.object({
     id: z.number().nullable()