Resolve latest patches per major Gradle version in CI workflow

[daniel-mohedano]

What Does This Do

• The Update smoke test latest versions workflow now also resolves the latest patches available per major release of Gradle
• This data, stored in latest-tool-versions.properties, is used by Gradle smoke tests to determine the oldest Gradle version that the project's TestKit supports and can be tested.

Motivation

Avoids the need of manually updating the oldest scenario every time the project's Gradle version is bumped to a new major release.

Additional Notes

test-environment-trigger: skip

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Add your completed PR to the merge queue by commenting /merge. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]

[datadog-prod-us1-4]

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

DataDog/apm-reliability/dd-trace-java | linux-java-spring-petclinic-sca-load-parallel     

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 2d37cab | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	13.95 s	13.94 s	[-0.7%; +0.7%] (no difference)
startup:insecure-bank:tracing:Agent	12.93 s	12.97 s	[-1.0%; +0.3%] (no difference)
startup:petclinic:appsec:Agent	16.87 s	16.67 s	[+0.4%; +2.0%] (maybe worse)
startup:petclinic:iast:Agent	16.95 s	17.00 s	[-1.3%; +0.7%] (no difference)
startup:petclinic:profiling:Agent	16.81 s	16.99 s	[-2.0%; -0.0%] (maybe better)
startup:petclinic:sca:Agent	16.87 s	16.85 s	[-0.8%; +1.1%] (no difference)
startup:petclinic:tracing:Agent	16.10 s	15.47 s	[-0.3%; +8.5%] (no difference)

Commit: 2d37cab5 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.