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/variants/input/User.input.ts

@@ -12,7 +12,6 @@ export const UserInputSchema = z.object({
     npiProviders: z.array(z.unknown()),
     claims: z.array(z.unknown()),
     insuranceCredentials: z.array(z.unknown()),
-    shoppingVendors: z.array(z.unknown()),
     updatedPayments: z.array(z.unknown()),
     backups: z.array(z.unknown()),
     backupDestinations: z.array(z.unknown()),
@@ -24,9 +23,7 @@ export const UserInputSchema = z.object({
     aiSettings: z.unknown().optional().nullable(),
     officeHours: z.unknown().optional().nullable(),
     officeContact: z.unknown().optional().nullable(),
-    procedureTimeslot: z.unknown().optional().nullable(),
-    insuranceContacts: z.array(z.unknown()),
-    patientConversations: z.array(z.unknown())
+    procedureTimeslot: z.unknown().optional().nullable()
 }).strict();
 
 export type UserInputType = z.infer<typeof UserInputSchema>;