fix(portal): remove invalid props from section component calls

The GRO-205/OOBE commit added sessionId/clientName props to Dashboard
and sessionId to PetProfiles/BillingPayments/Communication/AccountSettings
calls, but the Props interfaces for these components don't include those
props. TypeScript strict mode catches this.

Fix: remove the invalid props from calls where they're not accepted.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

apps/web/src/portal/CustomerPortal.tsx

@@ -125,19 +125,19 @@ export function CustomerPortal() {
     const sessionId = session?.id ?? null;
     switch (activeSection) {
       case "dashboard":
-        return <Dashboard onNavigate={handleNavClick} readOnly={!!isReadOnly} sessionId={sessionId} clientName={clientName} onReschedule={handleReschedule} />;
+        return <Dashboard onNavigate={handleNavClick} readOnly={!!isReadOnly} onReschedule={handleReschedule} />;
       case "appointments":
         return <AppointmentsSection readOnly={!!isReadOnly} sessionId={sessionId} />;
       case "pets":
-        return <PetProfiles readOnly={!!isReadOnly} sessionId={sessionId} />;
+        return <PetProfiles readOnly={!!isReadOnly} />;
       case "reports":
-        return <ReportCards sessionId={sessionId} />;
+        return <ReportCards />;
       case "billing":
-        return <BillingPayments readOnly={!!isReadOnly} sessionId={sessionId} />;
+        return <BillingPayments readOnly={!!isReadOnly} />;
       case "messages":
-        return <Communication readOnly={!!isReadOnly} sessionId={sessionId} />;
+        return <Communication readOnly={!!isReadOnly} />;
       case "settings":
-        return <AccountSettings readOnly={!!isReadOnly} sessionId={sessionId} />;
+        return <AccountSettings readOnly={!!isReadOnly} />;
     }
   };