Migrate version.gradle script plugin to Kotlin convention plugin

[bric3]

What does it do

Replaces the Groovy version.gradle script plugin with a convention plugin dd-trace-java.version-file.

There's 20 consumers they are now declarign it in plugins {} block (or apply plugin: where plugins {} is not available).

Adds tests for this plug-in.

Motivation

1. Project.exec {} is removed in Gradle 9. It is also incompatible with the configuration cache.
2. version.gradle is a Groovy script plugin, migrating to convention plugin is the way to go.

Additional Notes

Sub-PR of #10402, #11272.

[AlexeyKuznetsov-DD]

One more step in removing Groovy! Nice!

[pr-commenter]

Debugger benchmarks

Parameters

	Baseline	Candidate
baseline_or_candidate	baseline	candidate
ci_job_date	1778590352	1778590701
end_time	2026-05-12T12:54:02	2026-05-12T12:59:52
git_branch	master	bdu/gradle9-write-version-convention-plugin
git_commit_sha	710ca87	6ee8709
start_time	2026-05-12T12:52:33	2026-05-12T12:58:22

See matching parameters

	Baseline	Candidate
ci_job_id	1675698256	1675698256
ci_pipeline_id	112691016	112691016
cpu_model	Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz	Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
git_commit_date	1778589816	1778589816

Summary

Found 0 performance improvements and 0 performance regressions! Performance is the same for 9 metrics, 6 unstable metrics.

See unchanged results

scenario	Δ mean agg_http_req_duration_min	Δ mean agg_http_req_duration_p50	Δ mean agg_http_req_duration_p75	Δ mean agg_http_req_duration_p99	Δ mean throughput
scenario:noprobe	unstable [-26.531µs; +22.297µs] or [-8.493%; +7.138%]	unstable [-40.070µs; +34.891µs] or [-11.182%; +9.737%]	unstable [-52.266µs; +43.611µs] or [-13.886%; +11.587%]	unstable [-216.874µs; +118.264µs] or [-16.583%; +9.043%]	same
scenario:basic	same	same	same	unstable [-46.076µs; +77.824µs] or [-4.276%; +7.223%]	unstable [-151.601op/s; +151.601op/s] or [-6.367%; +6.367%]
scenario:loop	unsure [-8.767µs; -1.388µs] or [-0.098%; -0.016%]	same	same	same	same

Request duration reports for reports

gantt
title reports - request duration [CI 0.99] : candidate=None, baseline=None
dateFormat X
axisFormat %s
section baseline
noprobe (358.348 µs) : 316, 400
. : milestone, 358,
basic (312.499 µs) : 304, 321
. : milestone, 312,
loop (9.011 ms) : 9003, 9018
. : milestone, 9011,
section candidate
noprobe (355.759 µs) : 328, 384
. : milestone, 356,
basic (310.265 µs) : 302, 318
. : milestone, 310,
loop (9.015 ms) : 9007, 9022
. : milestone, 9015,

Loading

• baseline results

Scenario	Request median duration [CI 0.99]
noprobe	358.348 µs [316.48 µs, 400.217 µs]
basic	312.499 µs [303.594 µs, 321.404 µs]
loop	9.011 ms [9.003 ms, 9.018 ms]

• candidate results

Scenario	Request median duration [CI 0.99]
noprobe	355.759 µs [327.824 µs, 383.693 µs]
basic	310.265 µs [302.462 µs, 318.067 µs]
loop	9.015 ms [9.007 ms, 9.022 ms]

[sarahchen6]

🎉

[bric3]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-05-12 14:32:04 UTC ℹ️ Start processing command /merge

---

2026-05-12 14:32:12 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-05-12 15:08:09 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-05-12 16:26:04 UTC ℹ️ MergeQueue: This merge request was merged