chore(deps): update Gradle to v9.2.1

[github-actions]

Bumps scripts/update-gradle.sh from v8.14.3 to v9.2.1.

Auto-generated by a dependency updater.

[cursor]

Bug: Gradle wrapper JAR not updated with version bump

The distributionUrl was updated to Gradle 9.2.1, but the gradle-wrapper.jar binary file was not updated. When the wrapper distribution URL is changed, the wrapper JAR should also be regenerated or updated to ensure compatibility. This mismatch could cause build failures or unexpected behavior when developers or CI/CD systems use the wrapper.

 

[sentry]

Bug: Custom Test tasks will fail or be skipped after the Gradle 9.2.1 upgrade because they lack the now-required explicit testClassesDirs and classpath configurations.
_{Severity: CRITICAL | Confidence: High}

🔍 Detailed Analysis

The upgrade to Gradle 9.2.1 introduces a breaking change from Gradle 9.0 that affects custom Test tasks. Previously, these tasks implicitly used the default test source set's classpath. Now, they require explicit configuration. The codebase contains numerous custom Test tasks, such as systemTest in over 18 sample projects, which lack the necessary testClassesDirs and classpath properties. Consequently, after this upgrade, these test tasks will fail to find any test classes, leading to either build failures or, more critically, silently skipping the entire system test suite.

💡 Suggested Fix

For each custom Test task registration, such as tasks.register<Test>("systemTest"), explicitly configure the test classes and classpath. Add the following lines inside the task's configuration block:
testClassesDirs = sourceSets["test"].output.classesDirs
classpath = sourceSets["test"].runtimeClasspath

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: gradle/wrapper/gradle-wrapper.properties#L3

Potential issue: The upgrade to Gradle 9.2.1 introduces a breaking change from Gradle
9.0 that affects custom `Test` tasks. Previously, these tasks implicitly used the
default `test` source set's classpath. Now, they require explicit configuration. The
codebase contains numerous custom `Test` tasks, such as `systemTest` in over 18 sample
projects, which lack the necessary `testClassesDirs` and `classpath` properties.
Consequently, after this upgrade, these test tasks will fail to find any test classes,
leading to either build failures or, more critically, silently skipping the entire
system test suite.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 7822598}