fix(mobile): make iOS dev build install + EAS updates load on device

[jimprince]

Completes the mobile dev-channel repair (follow-up to #9). Verified by a real cloud iOS build reaching FINISHED with a matching published update.

Root causes fixed (each was hidden behind the previous)

1. CocoaPods install failed — Clerk auth pulled @clerk/expo → GoogleSignIn → AppCheckCore, whose deps GoogleUtilities/RecaptchaInterop can't link as static libs. Fix: plugins/withIosModularGooglePods.cjs sets :modular_headers => true for those pods.
2. Configure expo-updates — entry resolved to index.js; renamed index.ts → index.js + package.json main.
3. Fingerprint mismatch (the real reason updates never loaded) — Expo's iOS fingerprint hashed pnpm peer-hash store paths (.pnpm/<pkg>@<ver>_<hash>/) that differ between the Linux CI runner (which computes the fingerprint and publishes updates) and EAS's macOS build worker. So builds and updates got different runtimeVersions. Fix: fingerprint.config.cjs with a fileHookTransform normalizing those paths → stable, environment-independent fingerprint.

Verification

• Cloud iOS build 1db769c7 → FINISHED, runtimeVersion fb52eab3….
• EAS development update published at the same fb52eab3….
• vp check / vp run typecheck / mobile tests (192) green.

🤖 Generated with Claude Code