test(parametric): recognize v1 trace requests

[AlexeyKuznetsov-DD]

Motivation

Java can use trace protocol v1.0, but the helper only recognized /v0.4/traces, /v0.5/traces, and /v0.7/traces. Valid requests were filtered out, causing three client-computed-stats tests to report that no trace export request was received.

Changes

Includes native /v1.0/traces requests when locating span-carrying trace exports in the OTLP trace-metrics tests.

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• Anything but tests/ or manifests/ is modified ? I have the approval from R&P team
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added, removed or renamed?
  • Get a review from R&P team

[github-actions]

CODEOWNERS have been resolved as:

tests/parametric/test_otlp_trace_metrics.py                             @DataDog/system-tests-core @DataDog/apm-sdk-capabilities

[datadog-prod-us1-3]

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: cd649d3 | Docs | Datadog PR Page | Give us feedback!}