chore: update expo-server-sdk to version 3.15.0; reorganize push notifications documentation

- Updated expo-server-sdk in package.json from 3.10.0 to 3.15.0.
- Deleted outdated firebase-push-notifications.md and created new push-notifications.md for clarity.
- Updated navigation links in Nav.ts and README.md to point to the new push-notifications documentation.

Common/package.json

@@ -96,7 +96,7 @@
     "ejs": "^3.1.10",
     "elkjs": "^0.10.0",
     "esbuild": "^0.25.5",
-    "expo-server-sdk": "^3.10.0",
+    "expo-server-sdk": "^3.15.0",
     "express": "^4.21.1",
     "formik": "^2.4.6",
     "history": "^5.3.0",

Docs/Utils/Nav.ts

@@ -251,7 +251,7 @@ DocsNav.push({
     },
     {
       title: "Push Notifications",
-      url: "/docs/self-hosted/firebase-push-notifications",
+      url: "/docs/self-hosted/push-notifications",
     },
     {
       title: "SendGrid Inbound Email",

MobileApp/README.md

@@ -96,7 +96,7 @@ ServerUrlScreen → LoginScreen → MainTabNavigator (Home, Incidents, Alerts, S
 
 Native push notifications (iOS/Android) are powered by Expo Push and require no server-side configuration. The mobile app registers an Expo Push Token with the backend on login. The backend sends notifications via the public Expo Push API.
 
-Web push uses VAPID keys (configured separately). See the [Push Notifications docs](../Docs/Content/self-hosted/firebase-push-notifications.md) for details.
+Web push uses VAPID keys (configured separately). See the [Push Notifications docs](../Docs/Content/self-hosted/push-notifications.md) for details.
 
 ## Troubleshooting