Unprocessed Trace exception logs memory address instead of error message

**Reproduce**

Find a way to trigger this line https://github.com/aws/aws-xray-daemon/blob/4dce92e8eb72a88959337fb7bcc133f126772d6d/pkg/processor/batchprocessor.go#L106

And observe an error message that looks like this

`2025-11-07T22:49:42Z [Error] Unprocessed trace 1-690e7545-4f636120136ae307c2a705f4, segment: {0xc000016a50 0xc000016a60 0xc000016a70 {}}`

As you can see instead of printing the error message, segmentId, and error code, it prints the memory address of those things.

I suspect this issue was introduced in the aws sdk 1->2 update because it doesnt exist in 3.3.15

Start in pkg/processor/batchprocessor.go at line 106 and reproduce the unprocessed-trace path described in the issue. Inspect how the segment and error are formatted in the log, then verify that the output contains the error message, segment ID, and error code rather than memory addresses.

Written by the indexing model from the issue text.