Update codeowners file

[sarahchen6]

What Does This Do

Update CODEOWNERS file such that

• Shared tooling and modules are explicitly owned by @DataDog/apm-java - there is no longer a default team
• A few product paths are updated to include all tests under their domain

Motivation

RFC for "CODEOWNER File Expectations Across dd-trace-* Repositories": https://docs.google.com/document/d/1sRETEtnOf-ewrfuf_eQCs1nL8wbht2N7Dm9m5nrMJ1Y/edit?usp=sharing

Ensure that all code is properly and explicitly owned and protected by teams with the most context in that domain.

Additional Notes

In conjunction with these changes, all-files-are-owned via Datadog’s MergeGate mechanism should be enabled - this ensures that all new and existing files have assigned codeowners, according to the Code Ownership Service

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]

[datadog-prod-us1-4]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 58.30% (-0.06%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 6b37d5d | Docs | Datadog PR Page | Give us feedback!}

[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.82 s	14.71 s	[-0.2%; +1.8%] (no difference)
startup:insecure-bank:tracing:Agent	13.64 s	13.75 s	[-1.7%; +0.2%] (no difference)
startup:petclinic:appsec:Agent	17.44 s	17.37 s	[-0.6%; +1.3%] (no difference)
startup:petclinic:iast:Agent	17.27 s	17.53 s	[-2.3%; -0.6%] (maybe better)
startup:petclinic:profiling:Agent	17.41 s	16.77 s	[-0.8%; +8.5%] (no difference)
startup:petclinic:sca:Agent	16.72 s	17.26 s	[-7.3%; +1.0%] (no difference)
startup:petclinic:tracing:Agent	16.58 s	16.71 s	[-1.8%; +0.2%] (no difference)

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