Pin expo-age-range to 0.2.18 so the patch applies

The `^0.2.17` range floated up to 0.2.18 on reinstall, but pnpm matches
patchedDependencies by exact version, so the 0.2.17 patch was orphaned
(ERR_PNPM_UNUSED_PATCH) and the Swift concurrency fix never applied. Pin
to the exact resolved version and move the patch to match; the patch
context is identical in 0.2.18, so it applies cleanly.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

package.json

@@ -157,7 +157,7 @@
     "emoji-regex": "^10.4.0",
     "eventemitter3": "^5.0.1",
     "expo": "54.0.34",
-    "expo-age-range": "^0.2.17",
+    "expo-age-range": "0.2.18",
     "expo-application": "~7.0.8",
     "expo-blur": "~15.0.8",
     "expo-build-properties": "~1.0.10",