fix: default EAS composite actions to preview, not staging

.github/actions/eas-build/action.yml

@@ -4,9 +4,9 @@
 
 # ✍️ Description:
 # This is a composite action, which means it can be used in other actions.
-# This action is used to trigger an EAS Build for a specific environment (development, staging, production).
+# This action is used to trigger an EAS Build for a specific environment (development, preview, production).
 # This action accepts those inputs:
-#        `APP_ENV`, which is used to generate an APK for a specific environment (development, staging, production). We use staging by default.
+#        `APP_ENV`, which is used to generate an APK for a specific environment (development, preview, production). We use preview by default.
 #        `AUTO_SUBMIT`, false by default, set to true if you want to automatically submit your build to stores.
 #        `EXPO_TOKEN`, required, access token for your Expo account. https://expo.dev/settings/access-tokens
 #        `VERSION`, required, version of the app to build. used as the build message.
@@ -17,7 +17,7 @@
 #      - name: ⏱️ EAS Build
 #        uses: ./.github/actions/eas-build
 #        with:
-#          APP_ENV: staging
+#          APP_ENV: preview
 #          EXPO_TOKEN: ${{ secrets.EXPO_TOKEN }}
 #          VERSION: ${{ github.event.release.tag_name }}
 #          IOS: false
@@ -28,7 +28,7 @@ inputs:
   APP_ENV:
     description: 'APP_ENV (one of): development, preview, production'
     required: true
-    default: staging
+    default: preview
   AUTO_SUBMIT: # # TODO: we need to handle this too
     description: 'AUTO_SUBMIT (one of): true, false'
     required: true

.github/actions/setup-jdk-generate-apk/action.yml

@@ -5,23 +5,23 @@
 # ✍️ Description:
 # This is a composite action, which means it can be used in other actions.
 # This action is used to set up the JDK environment and generate an Android APK for testing.
-# This action accepts one input: `APP_ENV`, which is used to generate an APK for a specific environment (development, staging, production). We use staging by default.
+# This action accepts one input: `APP_ENV`, which is used to generate an APK for a specific environment (development, preview, production). We use preview by default.
 # Before generating the APK, we run a pre-build script to generate the necessary native folders based on the APP_ENV.
 # On success, the APK is generated at `./android/app/build/outputs/apk/release/app-release.apk`.
 
 # 👀 Example usage:
 #       - name : 📦 Set Up JDK + Generate Test APK
 #         uses: ./.github/actions/setup-jdk-generate-apk
 #         with:
-#           APP_ENV: 'staging'
+#           APP_ENV: 'preview'
 
 name: 'Setup  JDK + GRADLE + Generate APK'
 description: 'Setup  JDK + GRADLE + Generate APK'
 inputs:
   APP_ENV:
-    description: 'APP_ENV (one of): development, staging, production'
+    description: 'APP_ENV (one of): development, preview, production'
     required: true
-    default: staging
+    default: preview
 
 runs:
   using: composite

.github/workflows/e2e-android-eas-build.yml

@@ -94,7 +94,7 @@ jobs:
           profile: Nexus 6
           script: |
             adb install "${{ github.workspace }}/app-release.apk"
-            $HOME/.maestro/bin/maestro test .maestro/ --env=APP_ID=com.obytes.staging  --format junit
+            $HOME/.maestro/bin/maestro test .maestro/ --env=APP_ID=com.obytes.preview  --format junit
 
       - name: Upload artifacts
         if: always()

.github/workflows/e2e-android-maestro.yml

@@ -35,7 +35,7 @@ jobs:
       - name: 📦 Set Up JDK + Generate Test APK
         uses: ./.github/actions/setup-jdk-generate-apk
         with:
-          APP_ENV: staging
+          APP_ENV: preview
 
       - name: Upload Test APK
         uses: actions/upload-artifact@v3
@@ -49,4 +49,4 @@ jobs:
           api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
           app-file: ./android/app/build/outputs/apk/release/app-release.apk
           env: |
-            APP_ID=com.obytes.staging
+            APP_ID=com.obytes.preview

.github/workflows/e2e-android.yml

@@ -37,7 +37,7 @@ jobs:
       - name: 📦 Set Up JDK + Generate Test APK
         uses: ./.github/actions/setup-jdk-generate-apk
         with:
-          APP_ENV: staging
+          APP_ENV: preview
 
       - name: Upload Test APK
         uses: actions/upload-artifact@v3
@@ -102,7 +102,7 @@ jobs:
           profile: Nexus 6
           script: |
             adb install "${{ github.workspace }}/app-release.apk"
-            $HOME/.maestro/bin/maestro test .maestro/ --env=APP_ID=com.obytes.staging  --format junit
+            $HOME/.maestro/bin/maestro test .maestro/ --env=APP_ID=com.obytes.preview  --format junit
 
       - name: Upload artifacts
         if: always()

.github/workflows/eas-build-preview.yml

@@ -5,7 +5,7 @@
 # ✍️ Description:
 # This workflow is used to trigger a build on EAS for the QA environment.
 # It will run on every GitHub release published on the repo or can be triggered manually from the actions tab.
-# This workflow will use ./actions/eas-build action to trigger the build on EAS with staging env.
+# This workflow will use ./actions/eas-build action to trigger the build on EAS with preview env.
 
 # 🚨 GITHUB SECRETS REQUIRED:
 #         - EXPO_TOKEN: Expo token to authenticate with EAS