[winrid]

Gradle 9.4 requires JDK 17, so every release run of publish.yml has failed since 2.0.0 ("Gradle requires JVM 17 or later") and local publishes needed a manual JAVA_HOME.

• publish_to_repsy.sh uses the newest sdkman java/17.* candidate when one is installed and otherwise keeps the caller's JAVA_HOME (CI's setup-java). It prints the JDK it uses.
• Each module build runs in a subshell, so a failed build stops the script. Before this, set -e ignored failures inside the cd ... && ./gradlew ... && cd - chains, and the script went on from inside ./client (that's the chmod: cannot access './core/gradlew' error in the v3.1.0 run).
• publish.yml sets up JDK 17 instead of 11.

Verified by publishing v3.1.0 with this script from a shell whose default JDK is 21: it picked 17.0.17, all three modules built, and Repsy lists client, core and pubsub 3.1.0.