Enable Test_Config_LogInjection_128Bit_TradeId tests

[mtoffl01]

Motivation

128bit trace ID logging will be enabled by default in dd-trace-go as of this PR: DataDog/dd-trace-go#3086

Changes

• Enables Test_Config_LogInjection_128Bit_TradeId_Default and Test_Config_LogInjection_128Bit_TradeId_Disabled tests for dd-trace-go v1.72.0-dev+
• Modifies test logic for parsing the resulting log message, since the previous regex did not match the pattern for go (Go prints trace id and span id as separate entities, dd.trace_id and dd.span_id, instead of sub-entities of a great dd field e.g. "dd": {"trace_id": val, "span_id": val}

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• If PR title starts with [<language>], double-check that only <language> is impacted by the change
• No system-tests internal is modified. Otherwise, I have the approval from R&P team
• CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added (or removed)?
  • Get a review from R&P team

[cbeauchesne]

As the test logic is modified, I removed the prefix in the Pr title

[mtoffl01]

@cbeauchesne ,
This PR is failing the linter, but I had to change the test condition to check for 'message' in addition to "message" because it was failing otherwise; the json it's trying to match against looked like this: {'message': "key":"value",...}. I was surprised that "message" was not a sufficient match, but this was the only way I got it to work. What are your thoughts?

[cbeauchesne]

'message' and "message" are exactly the same in python, and the lint rules applied here requires to use the second.

I'm not really sure to understand what you want to do, could you add a meeting? we'll go trough this with zoom, it'll be easier.