refactor: Extract OTLP sender infrastructure to communication/otlp-exporter

[jbachorik]

What Does This Do

Moves the OTLP sender classes OtlpSender, OtlpSenderSupport, OtlpHttpSender, and OtlpGrpcSender into datadog.communication.otlp.

Adds OtlpResponse as the return type of the senders.

Adds OtlpCanonicalResourceAttributes. OtlpResourceAttributes in dd-trace-core delegates to it.

Motivation

The senders cannot move unchanged. OtlpSender.send returns RemoteApi.Response, and RemoteApi lives in dd-trace-core. A dependency from communication/otlp-exporter back to dd-trace-core would be circular. The senders therefore return the new OtlpResponse. dd-trace-core maps the response where it used RemoteApi.Response.

OtlpCanonicalResourceAttributes gives every OTLP signal the same set of resource attributes. The tracer and the profiler share one implementation, and there is one place to update it.

Additional Notes

Part of a 5-PR stack. Each PR bases on the previous one.

1. The payload and request body move (refactor: Move OtlpPayload and OTLP request bodies to communication/otlp-exporter #12880)
2. this PR: the sender extraction and the canonical resource attributes
3. RecordingData reference counting (feat(profiling): Reference-count RecordingData lifecycle #12869)
4. JFR to OTLP/P converter, profiling-otel, plus jafar 0.26.2 (feat(profiling): Add JFR to OTLP/P converter with CLI, benchmarks and validation #12870)
5. OTLP profiles export wiring (feat(profiling): Integrate OTLP profiles export into the agent #12871)

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
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[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	14.77 s	14.66 s	[-0.0%; +1.6%] (no difference)
startup:insecure-bank:tracing:Agent	13.54 s	13.59 s	[-1.1%; +0.3%] (no difference)
startup:petclinic:appsec:Agent	17.12 s	17.00 s	[-0.3%; +1.7%] (no difference)
startup:petclinic:iast:Agent	16.96 s	16.86 s	[-0.3%; +1.5%] (no difference)
startup:petclinic:profiling:Agent	16.52 s	16.78 s	[-2.6%; -0.6%] (maybe better)
startup:petclinic:sca:Agent	17.09 s	16.89 s	[+0.5%; +1.9%] (maybe worse)
startup:petclinic:tracing:Agent	16.02 s	16.09 s	[-1.6%; +0.6%] (no difference)

Commit: f36694bb · 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.