Enable 128bit trace ID logging by default

[mtoffl01]

What does this PR do?

Logs contain the full 128bits of the trace id by default. Can be disabled with DD_TRACE_128_BIT_TRACEID_LOGGING_ENABLED=false. Feature applies to tracer logs as well as our supported logger integrations: slog and logrus.

Motivation

Config consistency

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.
• Non-trivial go.mod changes, e.g. adding new modules, are reviewed by @DataDog/dd-trace-go-guild.
• For internal contributors, a matching PR should be created to the v2-dev branch and reviewed by @DataDog/apm-go.

Unsure? Have a question? Request a review!

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-02-13 23:03:41

Comparing candidate commit f8ea041 in PR branch mtoff/v2-log128bits with baseline commit 839b9bc in branch v2-dev.

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

scenario:BenchmarkSetTagMetric-24

• 🟩 execution_time [-4.963ns; -3.677ns] or [-3.888%; -2.881%]

[datadog-datadog-prod-us1]

Datadog Report

Branch report: mtoff/v2-log128bits
Commit report: 814544c
Test service: dd-trace-go

❌ 7 Failed (0 Known Flaky), 4327 Passed, 67 Skipped, 2m 11s Total Time

❌ Failed Tests (7)

This report shows up to 5 failed tests.

• TestHandleS3Operation - github.com/DataDog/dd-trace-go/contrib/aws/aws-sdk-go-v2/v2/internal/span_pointers - Details

  Expand for error

   Failed
   
   === RUN   TestHandleS3Operation
   --- FAIL: TestHandleS3Operation (0.00s)
  

• TestHandleS3Operation/basic_operation - github.com/DataDog/dd-trace-go/contrib/aws/aws-sdk-go-v2/v2/internal/span_pointers - Details

  Expand for error

   Failed
   
   === RUN   TestHandleS3Operation/basic_operation
       span_pointers_test.go:162: 
           	Error Trace:	/home/runner/work/dd-trace-go/dd-trace-go/contrib/aws/aws-sdk-go-v2/internal/span_pointers/span_pointers_test.go:162
           	Error:      	Should NOT be empty, but was []
           	Test:       	TestHandleS3Operation/basic_operation
           	Messages:   	Expected span links to not be empty
       --- FAIL: TestHandleS3Operation/basic_operation (0.00s)
   panic: runtime error: index out of range [0] with length 0 [recovered]
   ...
  

• TestFetchMessageFunctional - github.com/DataDog/dd-trace-go/contrib/segmentio/kafka-go/v2 - Details

  Expand for error

   Failed
   
   === RUN   TestFetchMessageFunctional
       kafka_test.go:316: 
           	Error Trace:	/home/runner/work/dd-trace-go/dd-trace-go/contrib/segmentio/kafka-go/kafka_test.go:316
           	Error:      	Not equal: 
           	            	expected: string("gosegtest")
           	            	actual  : <nil>(<nil>)
           	Test:       	TestFetchMessageFunctional
       kafka_test.go:337: 
   ...
  

• TestReadMessageFunctional - github.com/DataDog/dd-trace-go/contrib/segmentio/kafka-go/v2 - Details

  Expand for error

   Failed
   
   === RUN   TestReadMessageFunctional
       kafka_test.go:230: 
           	Error Trace:	/home/runner/work/dd-trace-go/dd-trace-go/contrib/segmentio/kafka-go/kafka_test.go:230
           	Error:      	Not equal: 
           	            	expected: string("gosegtest")
           	            	actual  : <nil>(<nil>)
           	Test:       	TestReadMessageFunctional
       kafka_test.go:251: 
   ...
  

• TestTelemetry - github.com/DataDog/dd-trace-go/v2/ddtrace/opentelemetry - Details

  Expand for error

   Failed
   
   === RUN   TestTelemetry
   --- FAIL: TestTelemetry (0.42s)