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

@@ -12,6 +12,7 @@ const npiproviderscalarwherewithaggregatesinputSchema = z.object({
   userId: z.union([z.lazy(() => IntWithAggregatesFilterObjectSchema), z.number().int()]).optional(),
   npiNumber: z.union([z.lazy(() => StringWithAggregatesFilterObjectSchema), z.string()]).optional(),
   providerName: z.union([z.lazy(() => StringWithAggregatesFilterObjectSchema), z.string()]).optional(),
+  sortOrder: z.union([z.lazy(() => IntWithAggregatesFilterObjectSchema), z.number().int()]).optional(),
   createdAt: z.union([z.lazy(() => DateTimeWithAggregatesFilterObjectSchema), z.coerce.date()]).optional()
 }).strict();
 export const NpiProviderScalarWhereWithAggregatesInputObjectSchema: z.ZodType<Prisma.NpiProviderScalarWhereWithAggregatesInput> = npiproviderscalarwherewithaggregatesinputSchema as unknown as z.ZodType<Prisma.NpiProviderScalarWhereWithAggregatesInput>;