feat: chatbot rendering provider override and NPI provider ordering

- AI chat extracts 'with provider <name>' and routes claim to that provider
- Claim form reads provider from sessionStorage before any async effects run,
  preventing saved claim/procedure data from overriding the chatbot selection
- NPI provider settings table shows Provider #1 / #2 labels with up/down
  reorder buttons; Provider #1 is always the default for claims
- Default provider now uses sortOrder instead of hardcoded 'Mary Scannell'
- Added sortOrder column to NpiProvider schema with migration

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

packages/db/shared/schemas/findFirstNpiProvider.schema.ts

@@ -14,6 +14,7 @@ export const NpiProviderFindFirstSelectSchema: z.ZodType<Prisma.NpiProviderSelec
     userId: z.boolean().optional(),
     npiNumber: z.boolean().optional(),
     providerName: z.boolean().optional(),
+    sortOrder: z.boolean().optional(),
     createdAt: z.boolean().optional(),
     user: z.boolean().optional(),
     claims: z.boolean().optional(),
@@ -28,6 +29,7 @@ export const NpiProviderFindFirstSelectZodSchema = z.object({
     userId: z.boolean().optional(),
     npiNumber: z.boolean().optional(),
     providerName: z.boolean().optional(),
+    sortOrder: z.boolean().optional(),
     createdAt: z.boolean().optional(),
     user: z.boolean().optional(),
     claims: z.boolean().optional(),