ci: Run the pre-commit formatter on the project's JDK

The pre-commit workflow set up Python but no Java, so google-java-format
ran on the runner's default JDK 17 and could not parse this project's
Java 25 sources — every file using an unnamed `_` binding or a record
pattern failed to parse. Those constructs predate this branch; the job
only fails when a pull request happens to touch such a file.

Adds the same setup-java step pull_request.yaml already uses, keyed off
.java-version, and bumps extenda/pre-commit-hooks to v0.16.1.

Verified locally across the matrix: on JDK 17 the formatter fails with
either jar version (1.28.0 cannot parse `_`, 1.36.1 throws LinkageError);
on JDK 25 both pass. The JDK is the fix, the bump is housekeeping.

Author: thced

.github/workflows/pre-commit.yml

@@ -12,6 +12,12 @@ jobs:
       - name: Setup Python
         uses: actions/setup-python@v7
 
+      - name: Setup Java
+        uses: actions/setup-java@v6
+        with:
+          distribution: temurin
+          java-version-file: .java-version
+
       - name: Run pre-commit
         uses: pre-commit/actions@v3.0.1
         with:

.pre-commit-config.yaml

@@ -17,7 +17,7 @@ repos:
     hooks:
       - id: editorconfig-checker
   - repo: https://github.com/extenda/pre-commit-hooks
-    rev: v0.15.0
+    rev: v0.16.1
     hooks:
       - id: google-java-formatter
       - id: commitlint