chore(config/tracer): migrate traceProtocol

[mtoffl01]

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-12-10 19:56:57

Comparing candidate commit c268dba in PR branch mtoff/traceProtocol with baseline commit b760677 in branch main.

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

[codecov]

Codecov Report

❌ Patch coverage is 26.92308% with 19 lines in your changes missing coverage. Please review.
✅ Project coverage is 54.33%. Comparing base (0fc0961) to head (c268dba).
⚠️ Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/config/config.go	9.52%	19 Missing ⚠️

Additional details and impacted files

Files with missing lines	Coverage Δ
ddtrace/tracer/log.go	86.51% <100.00%> (ø)
ddtrace/tracer/option.go	85.14% <100.00%> (+0.52%)	⬆️
ddtrace/tracer/writer.go	91.70% <100.00%> (ø)
internal/config/config.go	60.00% <9.52%> (-40.00%)	⬇️

... and 73 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.