fix: properly report codeowners on tests

[hannahkm]

What does this PR do?

Motivation

Reviewer's Checklist

• Changed code has unit tests for its functionality at or near 100% coverage.
• System-Tests covering this feature have been added and enabled with the va.b.c-dev version tag.
• There is a benchmark for any new code, or changes to existing code.
• If this interacts with the agent in a new way, a system test has been added.
• New code is free of linting errors. You can check this by running ./scripts/lint.sh locally.
• Add an appropriate team label so this PR gets put in the right place for the release notes.
• Non-trivial go.mod changes, e.g. adding new modules, are reviewed by @DataDog/dd-trace-go-guild.

Unsure? Have a question? Request a review!

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-10-21 14:13:12

Comparing candidate commit 06eb0ad in PR branch hannahkm/fix-codeowners with baseline commit bddbef7 in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 24 metrics, 0 unstable metrics.

[datadog-official]

⚠️ Tests

⚠️ Warnings

❄️ 1 New flaky test detected

TestEnqueuedTracesHealthMetric from github.com/DataDog/dd-trace-go/v2/ddtrace/tracer (Datadog)

Failed

=== RUN   TestEnqueuedTracesHealthMetric
    metrics_test.go:91: 
        	Error Trace:	/Users/runner/work/dd-trace-go/dd-trace-go/ddtrace/tracer/metrics_test.go:91
        	Error:      	Not equal: 
        	            	expected: 3
        	            	actual  : 0
        	Test:       	TestEnqueuedTracesHealthMetric
--- FAIL: TestEnqueuedTracesHealthMetric (0.00s)

ℹ️ Info

🧪 All tests passed

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 06eb0ad | Docs | Was this helpful? Give us feedback!}