build(native): update libdatadog to v41.0.0

[mabdinur]

Description

Updates ddtrace-py native dependencies without adding OTLP trace-metrics behavior:

• Upgrades every libdatadog crate from v40.0.0 to v41.0.0 and regenerates Cargo.lock.
• Updates the GitHub and GitLab system-test revisions to 692e9462ef7296cf1224c0d2bd3a3623a1bfe590 using scripts/update-system-tests-version.py.
• Extends the Linux OTel thread-context test to cover trace flags added in libdatadog v41.0.0.
• Updates the OTLP metrics payload test for typed resource attributes emitted by v41.

Testing

• cargo check --locked --manifest-path src/native/Cargo.toml
• scripts/lint checks

Risks

This updates the shared native dependency used by tracing, profiling, telemetry, remote configuration, and crash tracking.

Additional Notes

#19672 is stacked on this PR and contains the OTLP trace-metrics feature and release note.

[cit-pr-commenter-54b7da]

Codeowners resolved as

Resolved from the full PR diff against main using the target branch CODEOWNERS file.
CODEOWNERS team requests not listed below are not required by the current file set.

No remaining files require a CODEOWNERS review.

[cit-pr-commenter-54b7da]

Circular import analysis

⚠️ Existing circular imports

There are 5 circular imports that already exist on the base branch and have not been changed by this PR.

ddtrace.contrib.internal.pytorch._distributed -> ddtrace.contrib.internal.pytorch._rank_root -> ddtrace.contrib.internal.pytorch._distributed
ddtrace.contrib.internal.django.patch -> ddtrace.contrib.internal.django.response -> ddtrace.contrib.internal.django.patch
ddtrace.errortracking._handled_exceptions.bytecode_injector -> ddtrace.errortracking._handled_exceptions.callbacks -> ddtrace.errortracking._handled_exceptions.collector -> ddtrace.errortracking._handled_exceptions.bytecode_reporting -> ddtrace.errortracking._handled_exceptions.bytecode_injector
ddtrace.llmobs -> ddtrace.llmobs._evaluators -> ddtrace.llmobs._evaluators.format -> ddtrace.llmobs._experiment -> ddtrace.llmobs
ddtrace.appsec._asm_request_context -> ddtrace.appsec._iast._iast_request_context_base -> ddtrace.appsec._iast._iast_env -> ddtrace.appsec._iast.reporter -> ddtrace.appsec._exploit_prevention.stack_traces -> ddtrace.appsec._asm_request_context

[datadog-prod-us1-5]

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

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

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-08-13 17:29:58

Comparing candidate commit 1271bc5 in PR branch codex/otlp-trace-metrics-libdatadog with baseline commit 3a825cc in branch main.

Found 0 performance improvements and 8 performance regressions! Performance is the same for 614 metrics, 9 unstable metrics.

scenario:httppropagationextract-datadog_tracecontext_tracestate_not_propagated_on_trace_id_no_match

• 🟥 execution_time [+4.873µs; +5.245µs] or [+7.241%; +7.793%]

scenario:httppropagationinject-ids_only

• 🟥 execution_time [+2.407µs; +2.594µs] or [+11.342%; +12.224%]

scenario:iastaspects-lower_aspect

• 🟥 execution_time [+30.828µs; +37.681µs] or [+13.195%; +16.128%]

scenario:iastaspectsospath-ospathbasename_aspect

• 🟥 execution_time [+74.301µs; +80.091µs] or [+18.017%; +19.420%]

scenario:iastaspectssplit-rsplit_aspect

• 🟥 execution_time [+11.977µs; +14.183µs] or [+8.751%; +10.363%]

scenario:span-start

• 🟥 execution_time [+1.433ms; +1.616ms] or [+8.981%; +10.125%]

scenario:telemetryaddmetric-1-count-metric-1-times

• 🟥 execution_time [+252.097ns; +302.023ns] or [+9.362%; +11.216%]

scenario:tracer-small

• 🟥 execution_time [+32.718µs; +35.042µs] or [+9.381%; +10.047%]

[cit-pr-commenter-54b7da]

Dependency direction analysis

⚠️ Existing dependency direction violations

There are 256 dependency direction violations that already exist on the base branch and have not been changed by this PR.

Show existing violations (showing 5 of 256 highest severity)

ddtrace.internal.tracemethods -×-> ddtrace.trace  (internal-core -> product:tracing, score=134)
ddtrace.llmobs._integrations.openai -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=132)
ddtrace.llmobs._evaluators.runner -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=132)
ddtrace.llmobs._integrations.base -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=132)
ddtrace.debugging._signal.model -×-> ddtrace.trace  (product:debugging -> product:tracing, score=132)

To see all violations, download the layers-base.json and layers-pr.json artifacts from this CI job and run:

uv run --script scripts/import-analysis/layers.py compare layers-base.json layers-pr.json

[florentinl]

LGTM for otel thread context changes. Thank you for adding the test.