Waseel: driver capture, chat/calls, dispatch, and session fixes

Driver onboarding now photographs the licence, ID card and vehicle
registration and reads the credential fields off them, plus a camera-only
profile selfie riders check the arriving driver against. Adds in-app chat
and WebRTC calls, push-backed ride offers, ratings, cancellation and
payment sheets, settlement, and the owner dashboard endpoints behind them.

Camera permission on Android:
  - Declare CAMERA and READ_MEDIA_IMAGES in the manifest. expo-image-picker's
    own plugin never declares CAMERA, and Android denies a request for an
    undeclared permission instantly and silently — no dialog is ever shown,
    which is indistinguishable from the app not asking at all.
  - Handle canAskAgain: once Android stops showing the dialog, repeating why
    we need it is a dead end, so offer Open Settings instead (lib/capture-
    permission.ts), matching what the location flow already did.

Session: a 401 on a request that carried a token now ends the session
instead of being reinterpreted per-screen — driver-home had been reading it
as "this user has no driver profile" and showing an onboarding form to an
already-onboarded driver. Requests without a token are exempt so a failed
sign-in doesn't sign you out, and the notification is latched per token so
concurrent polls tear the session down once. (root) gains the auth guard
that turns that into the sign-in screen; app/index.tsx only guarded the way
in, leaving a session that ended mid-screen with nowhere to go.

Also ignore .uploads/ — it holds driver licence, ID and vehicle scans plus
profile photos, which are personal data and must not be committed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

components/pin-adjuster.web.tsx

@@ -0,0 +1,20 @@
+import { Text, View } from "react-native";
+
+import { useT } from "@/lib/i18n";
+import type { PinAdjusterProps } from "@/components/pin-adjuster";
+
+// react-native-maps does not support web, same as components/map.web.tsx.
+// The screen around this still works — the rider just can't drag a pin — so
+// the stub reports nothing and leaves whatever coordinate they arrived with
+// intact, rather than blocking the flow on a platform used only for testing.
+export const PinAdjuster = (_props: PinAdjusterProps) => {
+  const t = useT();
+
+  return (
+    <View className="flex-1 items-center justify-center bg-general-100 dark:bg-neutral-900">
+      <Text className="text-general-200 dark:text-neutral-400 text-center font-JakartaMedium px-8">
+        {t("components.map.webUnavailable")}
+      </Text>
+    </View>
+  );
+};