no gradle daemon so windows 2019 can use the cache.

in case somebody wonders about the confusing message that a daemon
is started, an explanation here:
https://discuss.gradle.org/t/no-daemon-switch-ineffective-if-jvm-settings-cause-new-fork/14919/7

.github/workflows/ci-gradle.yml

@@ -93,10 +93,10 @@ jobs:
 
       # Compile / Test / Package are separate steps so the reason for any failure is more obvious in GitHub UI
       - name: Compile
-        run: gradle -q compileJava
+        run: gradle -q compileJava --no-daemon
 
       - name: Test
-        run: gradle -q test
+        run: gradle -q test --no-daemon
 
       # The repeated "matrix.release_from_this_build" checks are messy, but I have not found a simple way to avoid them
       # See https://github.com/actions/runner/issues/662
@@ -121,6 +121,7 @@ jobs:
           GPG_PASSPHRASE: ${{ secrets.ARTIFACT_SIGNING_PASSPHRASE }}
         run: |
           gradle sign "-Pversion=${POM_VERSION}"\
+            "--no-daemon" \
             "-Psigning.gnupg.keyName=${GPG_KEYNAME}" \
             "-Psigning.gnupg.passphrase=${GPG_PASSPHRASE}"