[Draft; don't merge] v2.0.0-rc

[darccio]

What does this PR do?

This PR is a preview of the changes that will be merged into main for v2 release as github.com/DataDog/dd-trace-go/v2.

Motivation

These are the main motivations behind releasing a v2:

• Migrate from gopkg.in: this causes pain in enterprise customers.
• Long due refactor: moving away from interfaces in favor of concrete types in the API is a requirement to avoid situations where we had to hack a solution because adding functions caused breaking changes.
• Mitigate false-positive results from third party security scanners: due to our bloated go.mod pulling contrib’s dependencies. Also, remove deprecated dependencies’ contribs.
• Reduce library misuse: introduce better patterns, like using context to start spans to ensure trace propagation.
• Long backlog of proposals blocked waiting for a never-getting-planned v2.

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.
• Add an appropriate team label so this PR gets put in the right place for the release notes.

For Datadog employees:

• If this PR touches code that handles credentials of any kind, such as Datadog API keys, I've requested a review from @DataDog/security-design-and-guidance.
• This PR doesn't touch any of that.

Unsure? Have a question? Request a review!

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-01-22 16:57:05

Comparing candidate commit ee9fb69 in PR branch v2-dev with baseline commit 4f57a47 in branch main.

Some scenarios are present only in baseline or only in candidate runs. If you didn't create or remove some scenarios in your branch, this maybe a sign of crashed benchmarks 💥💥💥
Check Gitlab CI job log to find if any benchmark has crashed.

Scenarios present only in baseline:

• BenchmarkStartRequestSpan-24
• BenchmarkSampleWAFContext-24

Found 2 performance improvements and 11 performance regressions! Performance is the same for 39 metrics, 1 unstable metrics.

scenario:BenchmarkHttpServeTrace-24

• 🟥 allocated_mem [+237 bytes; +274 bytes] or [+2.493%; +2.883%]
• 🟥 allocations [+5; +5] or [+6.329%; +6.329%]
• 🟥 execution_time [+1.046µs; +1.204µs] or [+6.570%; +7.562%]

scenario:BenchmarkInjectW3C-24

• 🟥 execution_time [+124.845ns; +149.355ns] or [+3.118%; +3.730%]

scenario:BenchmarkPartialFlushing/Disabled-24

• 🟥 execution_time [+8.776ms; +11.958ms] or [+3.245%; +4.422%]

scenario:BenchmarkPartialFlushing/Enabled-24

• 🟥 execution_time [+11.825ms; +15.185ms] or [+4.311%; +5.536%]
• 🟩 avgHeapInUse(Mb) [-8.156MB; -1.464MB] or [-11.463%; -2.058%]

scenario:BenchmarkSetTagStringer-24

• 🟩 execution_time [-7.767ns; -4.433ns] or [-5.117%; -2.920%]

scenario:BenchmarkSingleSpanRetention/no-rules-24

• 🟥 execution_time [+8.352µs; +9.459µs] or [+3.471%; +3.931%]

scenario:BenchmarkSingleSpanRetention/with-rules/match-all-24

• 🟥 execution_time [+9.784µs; +11.183µs] or [+4.093%; +4.679%]

scenario:BenchmarkSingleSpanRetention/with-rules/match-half-24

• 🟥 execution_time [+10.229µs; +11.621µs] or [+4.279%; +4.861%]

scenario:BenchmarkStartSpan-24

• 🟥 execution_time [+87.290ns; +119.510ns] or [+3.911%; +5.354%]

scenario:BenchmarkTracerAddSpans-24

• 🟥 allocated_mem [+56 bytes; +57 bytes] or [+2.462%; +2.486%]

[github-actions]

This PR is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 10 days.