Keep the master build runner from being OOM-killed and give unit tests a bigger heap (#1895)

Every recent failure of the Android CI workflow ends with "The runner has
received a shutdown signal" 17-20 minutes in, while one flavour's R8 pass
overlaps another flavour's bundle packaging. That is the 16 GB runner VM being
killed for memory: the Gradle daemon runs with -Xmx8g and the Kotlin daemon
inherits the same 8g.

Build the three bundles in separate Gradle invocations so packaging of one
flavour never overlaps R8 of the next, cap the Kotlin daemon at 3g on CI, and
add an 8 GB swapfile as a safety net.

The PR check has separately been failing with OutOfMemoryError in
testModernDebugUnitTest; the Gradle test worker default is 512m and the
Robolectric suite is over 1200 tests, so raise it to 4g.

Co-authored-by: Utkarsh Dalal <utkarsh.dalal@toptal.com>

Author: utkarshdalal

.github/workflows/app-release-signed.yml

@@ -23,6 +23,13 @@ jobs:
 
     steps:
     - uses: actions/checkout@v4
+    - name: Add swap
+      run: |
+        sudo fallocate -l 8G /mnt/swapfile.ci
+        sudo chmod 600 /mnt/swapfile.ci
+        sudo mkswap /mnt/swapfile.ci
+        sudo swapon /mnt/swapfile.ci
+        free -m
     - name: set up Java 17
       uses: actions/setup-java@v4
       with:
@@ -81,7 +88,11 @@ jobs:
         yes | "$SDKMANAGER" --install "build-tools;34.0.0"
 
     - name: Build with Gradle
-      run: ./gradlew :app:bundleLegacyRelease :app:bundleModernRelease :app:bundleLegacyXrRelease
+      run: |
+        ./gradlew -Pkotlin.daemon.jvmargs=-Xmx3g :app:bundleLegacyRelease
+        ./gradlew -Pkotlin.daemon.jvmargs=-Xmx3g :app:bundleModernRelease
+        ./gradlew -Pkotlin.daemon.jvmargs=-Xmx3g :app:bundleLegacyXrRelease
+        free -m
 
     - name: Stage bundles
       run: |

app/build.gradle.kts

@@ -229,6 +229,7 @@ android {
     testOptions {
         unitTests {
             isIncludeAndroidResources = true
+            all { it.maxHeapSize = "4g" }
         }
     }