ci: disable Gradle daemon reuse in release build

The shared runner host keeps Gradle daemons alive for up to 3 hours
and hands them to the next matching build regardless of which
project started them. A daemon warmed by an unrelated checkout (even
a local devbox test build) can serve this project's CI run next,
carrying over stale in-memory classpath state and producing
inconsistent "package android.app does not exist" failures.
Disabling the daemon for this one step keeps dependency/wrapper
caches shared while avoiding the live-process contamination.

.forgejo/workflows/release.yml

@@ -27,6 +27,12 @@ jobs:
           STORE_PASSWORD: ${{ secrets.STORE_PASSWORD }}
           KEY_ALIAS:      ${{ secrets.KEY_ALIAS }}
           KEY_PASSWORD:   ${{ secrets.KEY_PASSWORD }}
+          # This host runs other projects' builds too, and Gradle daemons
+          # persist across them. A daemon warmed by a different checkout
+          # can serve this build next, carrying over stale classpath state.
+          # ~/.gradle/caches (dependency jars, wrapper dists) stays shared
+          # and warm; only the long-lived daemon process is avoided.
+          GRADLE_OPTS: -Dorg.gradle.daemon=false
         run: |
           env -u GITHUB_TOKEN -u GH_TOKEN -u JAVA_HOME \
             devbox run -- flutter build apk --release