Fix map failing to render, dedupe expo-crypto

The home screen passed its FlatList header as `ListHeaderComponent={() =>
(...)}`. VirtualizedList renders a function-valued header prop as
`<HeaderComponent />`, so a fresh arrow function on each render is a fresh
element type: React unmounted the entire header subtree — MapView included —
and mounted a new one. Home re-renders several times on mount (useFetch
loading->data, useUserLocation pending->granted, session resolve), and
recreating the Android GoogleMap surface each time left it grey with the
Google logo and tiles that never finished loading.

Pass the header as an element instead so the type stays stable and MapView
mounts once. The same `() => (...)` pattern in ListEmptyComponent here, and in
rides.tsx and confirm-ride.tsx, cost needless remounts of list chrome and
DriverCards; fixed alongside.

Also pin expo-crypto to ~13.0.2. It was ^57.0.1 — a wrong-major native module
for SDK 51 that nothing in the app imports. npm hoisted it to the top level
and gave expo-auth-session a nested 13.0.2 to satisfy its ~13.0.0 constraint,
leaving two copies of one native module in the tree for autolinking to choose
between.

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

app.config.js

@@ -12,9 +12,22 @@ const LOCATION_PERMISSION =
 
 module.exports = ({ config }) => {
   if (!googleMapsApiKey) {
-    console.warn(
-      "[app.config] EXPO_PUBLIC_GOOGLE_API_KEY is not set — maps will render blank on Android.",
-    );
+    const message =
+      "EXPO_PUBLIC_GOOGLE_API_KEY is not set — the Android manifest will have no " +
+      "Maps key and the map will render blank.";
+
+    // `.env` is gitignored, so it is never uploaded to EAS. Unless the key is
+    // also registered as an EAS environment variable the build silently
+    // produces a keyless APK, and the blank map only shows up on the device.
+    // Fail the build here rather than shipping that.
+    if (process.env.EAS_BUILD) {
+      throw new Error(
+        `[app.config] ${message} Register it with \`eas env:create\` (or in the ` +
+          "EAS dashboard) for this build profile.",
+      );
+    }
+
+    console.warn(`[app.config] ${message}`);
   }
 
   return {