fix(mobile): make expo-modules-autolinking resolvable from the app

pnpm 11 ignores node-linker=hoisted in .npmrc, so node_modules uses the
isolated layout. Expo evaluates expo's react-native.config.js through the
apps/mobile/node_modules/expo symlink, where require('expo-modules-autolinking')
fails silently; autolinking then guessed the import from the Gradle namespace
(expo.core.ExpoModulesPackage) and the release Java compile failed.

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

apps/mobile/package.json

@@ -17,6 +17,7 @@
     "expo": "~53.0.20",
     "expo-build-properties": "~0.14.8",
     "expo-constants": "~17.1.7",
+    "expo-modules-autolinking": "~2.1.15",
     "expo-status-bar": "~2.2.3",
     "i18next": "^25.2.1",
     "react": "19.0.0",

pnpm-lock.yaml

@@ -38,6 +38,9 @@ importers:
       expo-constants:
         specifier: ~17.1.7
         version: 17.1.8(expo@53.0.27(@babel/core@7.29.7)(react-native@0.79.6(@babel/core@7.29.7)(@types/react@19.0.14)(react@19.0.0)(supports-color@10.2.2))(react@19.0.0)(supports-color@10.2.2))(react-native@0.79.6(@babel/core@7.29.7)(@types/react@19.0.14)(react@19.0.0)(supports-color@10.2.2))
+      expo-modules-autolinking:
+        specifier: ~2.1.15
+        version: 2.1.15
       expo-status-bar:
         specifier: ~2.2.3
         version: 2.2.3(react-native@0.79.6(@babel/core@7.29.7)(@types/react@19.0.14)(react@19.0.0)(supports-color@10.2.2))(react@19.0.0)