Automate upload to Google Play

This commit updates the `android-release_ci.yml` workflow to automatically upload release builds to the Google Play Store.

A new step, "Upload to Google Play," is added to the release job, which uses the `r0adkll/upload-google-play@v1` action. This step uploads the generated AAB file to the internal track. The workflow now also includes minor formatting adjustments.

Author: CreativeCodeCat

.github/workflows/android-release_ci.yml

@@ -66,20 +66,20 @@ jobs:
         shell: bash
         run: |
           set -e
-      
+          
           APK=$(find app/build/outputs/apk -name "*.apk" -type f | head -n 1)
           AAB=$(find app/build/outputs/bundle -name "*.aab" -type f | head -n 1)
           MAPPING=$(find app/build/outputs/mapping -name "mapping.txt" -type f | head -n 1)
-      
+          
           echo "Detected APK: $APK"
           echo "Detected AAB: $AAB"
           echo "Detected mapping: $MAPPING"
-      
+          
           if [[ -z "$APK" || -z "$AAB" ]]; then
             echo "❌ APK or AAB not found"
             exit 1
           fi
-      
+          
           echo "apk=$APK" >> "$GITHUB_OUTPUT"
           echo "aab=$AAB" >> "$GITHUB_OUTPUT"
           echo "mapping=$MAPPING" >> "$GITHUB_OUTPUT"
@@ -112,6 +112,15 @@ jobs:
           tag: ${{ github.ref }}
           overwrite: true
 
+      - name: Upload to Google Play
+        uses: r0adkll/upload-google-play@v1
+        with:
+          serviceAccountJsonPlainText: ${{ secrets.PLAY_SERVICE_ACCOUNT_JSON }}
+          packageName: app.mlauncher
+          releaseFiles: ${{ steps.detect_artifacts.outputs.aab }}
+          track: internal
+          status: completed
+
       - name: Set up Node.js
         uses: actions/setup-node@v6
         with:
@@ -123,4 +132,4 @@ jobs:
           DISCORD_ROLEID: ${{ secrets.DISCORD_ROLEID }}
         run: |
           # Run your Discord release script
-          node post-discord-release.js
+          node post-discord-release.js