[BUG]: Fuzz function FuzzParseTraceparent - Inconsistent trace id parsing

[edznux-dd]

Tracer Version(s)

Head (f92a95e4313dda76ac10592731652e282e9fd66b)

Go Version(s)

go version go1.23.5 linux/amd64

Bug Report

Running the already existing fuzz test causes a test failure for FuzzParseTraceparent here.

This specific test failure is cause by a "space" character in the value of the provided header, but I'm not sure if it's a tracer bug or simple a issue in the test itself.

Note: I believe these fuzz tests are not run regularly part of CI. But as we will soon start to run these frequently internally, it'd be nice to get this fixed

Reproduction Code

On main branch:

cd ddtrace/tracer/
go test -fuzz FuzzParseTraceparent -run FuzzParseTraceparent

should trigger quickly a failure. Otherwise, adding {"01", " 00000000000000000000000000000001", "0000000000000001", "0"}, to the test case testCases and simply running go test -run FuzzParseTraceparent should be enough.

Error Logs

--- FAIL: FuzzParseTraceparent (0.00s)
    --- FAIL: FuzzParseTraceparent/827e72a16a7238a5 (0.00s)
        textmap_test.go:2441: Inconsistent trace id parsing:
            					got: 00000000000000000000000000000001
            					wanted:  00000000000000000000000000000001
            					for header of: 01- 00000000000000000000000000000001-0000000000000001-0
FAIL

Go Env Output

No response