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/UserCreateResult.schema.ts

@@ -11,7 +11,6 @@ export const UserCreateResultSchema = 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()),
@@ -23,7 +22,5 @@ export const UserCreateResultSchema = z.object({
   aiSettings: z.unknown().optional(),
   officeHours: z.unknown().optional(),
   officeContact: z.unknown().optional(),
-  procedureTimeslot: z.unknown().optional(),
-  insuranceContacts: z.array(z.unknown()),
-  patientConversations: z.array(z.unknown())
+  procedureTimeslot: z.unknown().optional()
 });