Release workflows: use JDK 17 to match project target (#3771)

pom.xml sets <maven.compiler.release>17</maven.compiler.release> (since
#3579, "Bump minimum Java version to 17"), but release-prepare-rc.yml
and release-publish.yml still set up JDK 11. The mismatch produces
"class file version 61.0 vs. 55.0" errors when the release build runs
under Java 11. Update both workflows to JDK 17 (setup-java step name
and java-version) so the runtime matches the compile target.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Author: RussellSpitzer

.github/workflows/release-prepare-rc.yml

@@ -56,11 +56,11 @@ jobs:
           fetch-depth: 0
           token: ${{ secrets.GITHUB_TOKEN }}
 
-      - name: Set up JDK 11
+      - name: Set up JDK 17
         uses: actions/setup-java@dd06d9cba3e5552c54d9f8ea23572deb30010f7c # v6.0.0
         with:
           distribution: temurin
-          java-version: '11'
+          java-version: '17'
 
       - name: Import GPG key and configure Git
         env:

.github/workflows/release-publish.yml

@@ -65,11 +65,11 @@ jobs:
           fetch-depth: 0
           token: ${{ secrets.GITHUB_TOKEN }}
 
-      - name: Set up JDK 11
+      - name: Set up JDK 17
         uses: actions/setup-java@dd06d9cba3e5552c54d9f8ea23572deb30010f7c # v6.0.0
         with:
           distribution: temurin
-          java-version: '11'
+          java-version: '17'
 
       - name: Install Subversion
         run: sudo apt-get update -q && sudo apt-get install -q -y subversion