[ThoSap]

Gradle
https://docs.gradle.org/9.9.0/release-notes.html
https://docs.gradle.org/9.9.0/userguide/upgrading_version_9.html

Why

Keep the build on the latest Gradle 9.x release. Follows #84 (9.8.2), so only the changes of 9.9.0 apply here.

What changed

The build runs on Gradle 9.9.0 and has no Gradle deprecation warning left.

1. The Gradle Wrapper goes from 9.8.2 to 9.9.0. The wrapper task ran twice, so gradle-wrapper.jar comes from 9.9.0 too. gradlew and gradlew.bat are the same as in 9.8.2.
2. distributionSha256Sum is the value from the official checksum file, with the comment # https://gradle.org/release-checksums/ above it, as in the other projects (checksum and its comment).
3. gradle.properties sets org.gradle.tooling.parallel=true. Since Gradle 9.8.0, the IDE sync gives a deprecation warning when the build relies on the implicit value, and Gradle 10 makes it an error. true keeps the current behavior.
4. Every ./gradlew call in the readme has --console=colored (Gradle calls in the readme), like the Makefile and the workflows already do.
5. The Error Prone Gradle plugin goes from 5.1.1 to 5.2.0 (Error Prone plugin version), the same version as in the other projects. 5.1.1 already fixes the Configuration.setVisible(boolean) deprecation.
6. The nested class exclude comment in build.gradle.kts now says what the $* exclude from Update the Gradle Wrapper to 9.8.2 #84 is for: a pattern ending in a class name does not match its @Nested classes (Outer$Inner). Only the comment changes.

Deprecation warnings

None. --warning-mode=all shows no Gradle deprecation and no Kotlin DSL w: warning, and the build reports no problems. The Project.getProperties warning of the Quarkus Gradle plugin that #84 listed is gone since Quarkus 3.40.1.2.

Review notes

• 9.9.0 applies test filters also to JUnit Platform tests that are not methods (for example ArchUnit @ArchTest fields). This project has no ArchUnit tests and the CI does not use --tests, so nothing changes.
• 9.9.0 fails when Gradle runs in a directory inside the build that is not a project directory. No workflow runs ./gradlew outside the root directory.
• The readme calls ../gradlew in Getting started (../gradlew :operator:quarkusBuild). The ../ looks wrong, but this PR leaves it as it is.

Generated files

• gradle/wrapper/gradle-wrapper.jar is a binary file written by the wrapper task. The change in build.gradle.kts is a comment only.

Risk: needs a human review, assessed at 36a1f73

• The self-review found nothing, and no question for the reviewer is left. Every changed file had a full review, with a second opinion from GPT, except the comment-only change in build.gradle.kts.
• The repository does not run the self-review freshness Action, so a later push would not take away a risk:low label. That is why the PR has no label.