Migrate dd-trace-core groovy files to java part 14

[jpbempel]

What Does This Do

we migrate 3 tests from traceAgentTest module

Motivation

this is part of the effort to migrate groovy tests to Java/JUnit
part1: #11053
part2: #11062
part3: #11085
part4: #11146
part5: #11217
part6: #11362
part7: #11374
part8: #11437
part9: #11488
part10: #11543
part11: #11566
part12: #11619
part13: #12253

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: [PROJ-IDENT]

[dd-octo-sts]

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: 41dae6b7d8

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[datadog-datadog-prod-us1]

After DDApiIntegrationTest runs locally, JUnit does not run the parent container cleanup. The Docker agent stays active.

_{Open Bits AI session}

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

[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.02 s	14.05 s	[-1.1%; +0.6%] (no difference)
startup:insecure-bank:tracing:Agent	12.86 s	13.06 s	[-2.3%; -0.7%] (maybe better)
startup:petclinic:appsec:Agent	16.87 s	16.76 s	[-0.3%; +1.7%] (no difference)
startup:petclinic:iast:Agent	16.95 s	16.94 s	[-0.9%; +1.0%] (no difference)
startup:petclinic:profiling:Agent	16.79 s	16.83 s	[-1.2%; +0.8%] (no difference)
startup:petclinic:sca:Agent	16.82 s	16.39 s	[+1.7%; +3.5%] (significantly worse)
startup:petclinic:tracing:Agent	16.10 s	16.11 s	[-0.8%; +0.7%] (no difference)

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