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>

lib/utils.ts

@@ -56,6 +56,35 @@ export function normalizePhone(raw: string): string {
   return `+961${cleaned.replace(/^0+/, "")}`;
 }
 
+/**
+ * A lat/lng box that fully contains a circle of `radiusMeters` around a point.
+ *
+ * Used as a cheap first pass before the exact great-circle test: the box is
+ * something an index can answer, so the database only hands back the handful
+ * of rows worth measuring properly. It over-selects at the corners, which is
+ * why callers still filter with `haversine` afterwards.
+ */
+export function boundingBox(
+  latitude: number,
+  longitude: number,
+  radiusMeters: number,
+): { minLat: number; maxLat: number; minLng: number; maxLng: number } {
+  // A degree of latitude is ~111.32 km everywhere; a degree of longitude
+  // shrinks with the cosine of the latitude. The cos is floored so the box
+  // stays finite near the poles instead of dividing by zero.
+  const latDelta = radiusMeters / 111_320;
+  const lngDelta =
+    radiusMeters /
+    (111_320 * Math.max(Math.cos((latitude * Math.PI) / 180), 0.01));
+
+  return {
+    minLat: latitude - latDelta,
+    maxLat: latitude + latDelta,
+    minLng: longitude - lngDelta,
+    maxLng: longitude + lngDelta,
+  };
+}
+
 // Great-circle distance between two lat/lng points, in meters. Used for
 // nearest-driver matching and "X m away" POI chips. Haversine formula.
 export function haversine(