chore(ci): bump hardcoded datadog-trace-agent image from 7.31.0 to 7.81.3

[ghost]

What

Bumps the hardcoded datadog-trace-agent service image in tests/integration/datadog-agent/config/compose.yaml from docker.io/datadog/agent:7.31.0 to docker.io/datadog/agent:7.81.3 — the latest stable Agent v7 release per DataDog/datadog-agent release.json (last_stable.7 = 7.81.3).

Why

This pin bypasses the integration test's matrix.version entirely (the sibling datadog-agent service correctly floats via ${CONFIG_VERSION}, which is currently ["7"]). Being hardcoded, it doesn't drift forward automatically and had fallen ~50 minor versions behind current stable.

Scope / what this does NOT touch

• Only the datadog-trace-agent service's image: line changes. The datadog-agent service in the same file (using ${CONFIG_VERSION}) is untouched.
• No other Datadog Agent pins in the repo needed changes:
  • tests/integration/datadog-agent/config/test.yaml (version: ["7"]), tests/integration/datadog-traces/config/test.yaml, tests/integration/datadog-logs/config/test.yaml, tests/integration/datadog-metrics/config/test.yaml (all [latest]), and tests/e2e/datadog-logs/config/test.yaml (["latest","6","7"]) are floating tags — no action needed.
  • tests/e2e/datadog-metrics/config/test.yaml pins agent_version: ["7.80.4", "6"] as a deliberate regression pin (see comment in that file referencing datadog_agent source: support Datadog v3 series metrics intake API #25790 — Agent 7.81.0 defaulted metrics submission to the v3 series intake API, which Vector's datadog_agent source does not yet parse). I verified in src/sources/datadog_agent/metrics.rs that only api/v1/series, api/v2/series, and api/beta/sketches routes are registered — no v3 route exists yet. This pin was intentionally left unchanged; upgrading it would break that e2e test until v3 series support lands.

Diff

   datadog-trace-agent:
-    image: docker.io/datadog/agent:7.31.0
+    image: docker.io/datadog/agent:7.81.3

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[ghost]

 

⚠️ Warnings

🚦 1 Pipeline job failed

CLA Assistant | CLAAssistant     

See error

Could not update the JSON file. Repository is archived and read-only.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

Useful? React with 👍 / 👎

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

[vectordotdev-bot]

I have read the CLA Document and I hereby sign the CLA

[thomasqueirozb]

recheck

[ghost]

I have read the CLA Document and I hereby sign the CLA

[thomasqueirozb]

recheck