Migrate OpenTelemetry smoke test to JUnit

[PerfectSlayer]

What Does This Do

This PR migrates the OpenTelemetry smoke tests to the new JUnit smoke test framework.

Motivation

The new tests checks the whole trace structures and span values, in addition to trace payload validity and invariants.

Additional Notes

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
• Once approved, use merge queue to merge the PR

Jira ticket: APMLP-1247

[datadog-datadog-prod-us1-2]

More details

The JUnit migration preserves the OpenTelemetry smoke application launch and validates its one annotated trace plus ten sequential manual traces with the new backend assertions. No diff-only behavioral regression was confirmed; no additional tests recommended because the existing application shape is deterministic and the attempted module execution was blocked by unavailable Gradle/JDK tooling.

Was this helpful? React 👍 or 👎

_{📊 Validated against 3 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit 9eece4a · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9eece4ad18

ℹ️ 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".

[chatgpt-codex-connector]

Preserve the 30-second trace polling window

On slower CI workers or JVM variants where agent startup and trace delivery take more than 10 seconds, this migration can now fail even though the application still completes within its intended 30-second allowance: the deleted test's defaultPoll waited 30 seconds, while this call uses Traces.assertTraces's 10-second default and TIMEOUT_SECONDS is applied only afterward to the process wait. Pass the 30-second timeout to the trace assertion as well so the migration does not shorten the trace-delivery deadline.

Useful? React with 👍 / 👎.

[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.01 s	14.01 s	[-0.7%; +0.8%] (no difference)
startup:insecure-bank:tracing:Agent	12.87 s	13.03 s	[-2.0%; -0.4%] (maybe better)
startup:petclinic:appsec:Agent	16.93 s	17.00 s	[-1.4%; +0.5%] (no difference)
startup:petclinic:iast:Agent	17.07 s	17.04 s	[-0.5%; +0.9%] (no difference)
startup:petclinic:profiling:Agent	16.92 s	17.06 s	[-2.1%; +0.5%] (no difference)
startup:petclinic:sca:Agent	16.73 s	16.53 s	[+0.4%; +2.0%] (maybe worse)
startup:petclinic:tracing:Agent	16.19 s	16.19 s	[-1.0%; +1.0%] (no difference)

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