debugger/symdb: add upload metadata fields to upload event message

[andreimatei]

Add the following fields to the SymDB upload event message that accompanies each multipart upload:

• "version" (top-level): the service version
• "language" (top-level): "java"
• "upload_id" (top-level): a UUID generated once per SymbolSink instance, shared by all batches uploaded by the sink
• "batch_num" (top-level): 1-indexed counter incremented per upload
• "final" (top-level): always false; the Java tracer continuously uploads new code as classes get loaded, so there is no defined end-of-upload point
• "attachment_size" (top-level): size in bytes of the (compressed) attachment payload

Some of these fields are new, to be used by the backend in the future. Others duplicate info that was already included in the attachment; by duplicating some metadata out of the SymDB attachment body into the EvP event body, the backend can populate per-attachment bookkeeping without downloading the attachment.

[github-actions]

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

• Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a82745bb27

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[pr-commenter]

Debugger benchmarks

Parameters

	Baseline	Candidate
baseline_or_candidate	baseline	candidate
ci_job_date	1778281491	1778281837
end_time	2026-05-08T23:06:17	2026-05-08T23:12:03
git_branch	master	andrei/symdb-upload-fields
git_commit_sha	7e99f00	875f094
start_time	2026-05-08T23:04:52	2026-05-08T23:10:38

See matching parameters

	Baseline	Candidate
ci_job_id	1669639392	1669639392
ci_pipeline_id	112290209	112290209
cpu_model	Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
git_commit_date	1778279590	1778279590

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 [-18.452µs; +47.427µs] or [-6.415%; +16.487%]	unstable [-31.447µs; +63.204µs] or [-9.474%; +19.042%]	unstable [-37.476µs; +72.868µs] or [-10.817%; +21.034%]	unstable [-288.513µs; +188.886µs] or [-21.837%; +14.297%]	same
scenario:basic	same	same	same	unstable [-436.358µs; -168.901µs] or [-33.428%; -12.939%]	unstable [-136.485op/s; +136.485op/s] or [-5.459%; +5.459%]
scenario:loop	same	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 (331.92 µs) : 304, 360
.   : milestone, 332,
basic (294.041 µs) : 288, 300
.   : milestone, 294,
loop (8.987 ms) : 8982, 8993
.   : milestone, 8987,
section candidate
noprobe (347.799 µs) : 291, 405
.   : milestone, 348,
basic (296.403 µs) : 289, 304
.   : milestone, 296,
loop (8.988 ms) : 8982, 8993
.   : milestone, 8988,

Loading

• baseline results

Scenario	Request median duration [CI 0.99]
noprobe	331.92 µs [303.69 µs, 360.15 µs]
basic	294.041 µs [288.079 µs, 300.003 µs]
loop	8.987 ms [8.982 ms, 8.993 ms]

• candidate results

Scenario	Request median duration [CI 0.99]
noprobe	347.799 µs [290.782 µs, 404.816 µs]
basic	296.403 µs [288.639 µs, 304.167 µs]
loop	8.988 ms [8.982 ms, 8.993 ms]