chore(mobile): commit google-services.json for EAS cloud builds

Was gitignored under the assumption it should be redownloaded per
clone, but a cloud EAS build clones from git and won't see a gitignored
file at all — the build would fail without it (app.json's
android.googleServicesFile references this path). Its contents (API
key, app/project IDs) aren't secret: Google restricts access by
package name and SHA fingerprint, not by hiding the file, same as most
public Firebase Android repos.

mobile/.gitignore

@@ -37,9 +37,10 @@ yarn-error.*
 .env*
 !.env.example
 
-# Firebase (FCM push credentials) — project-specific, redownload from
-# Firebase Console (org.pawfeed.app app) on a fresh clone instead of committing
-google-services.json
+# google-services.json IS committed (see below) — EAS cloud builds clone
+# from git and need it present; its contents (API key, app ID) aren't
+# secret (Google restricts access by package name/SHA fingerprint, not by
+# hiding this file — same practice as most public Firebase Android repos).
 
 # typescript
 *.tsbuildinfo

mobile/google-services.json

@@ -0,0 +1,29 @@
+{
+  "project_info": {
+    "project_number": "1048292105810",
+    "project_id": "pawfeed-93394",
+    "storage_bucket": "pawfeed-93394.firebasestorage.app"
+  },
+  "client": [
+    {
+      "client_info": {
+        "mobilesdk_app_id": "1:1048292105810:android:c590c99b9778698d02098b",
+        "android_client_info": {
+          "package_name": "org.pawfeed.app"
+        }
+      },
+      "oauth_client": [],
+      "api_key": [
+        {
+          "current_key": "AIzaSyA2O8eO1K0A5IYSSVdUq8QrG_fUAKqxidY"
+        }
+      ],
+      "services": {
+        "appinvite_service": {
+          "other_platform_oauth_client": []
+        }
+      }
+    }
+  ],
+  "configuration_version": "1"
+}