fix(integration): extend Windows assertion timeouts (#1859)

## Summary
- Extend assertion-level timeouts to 60s for Windows-enabled integration tests.
- Leave per-test suite timeouts, stability durations, and negative observation windows unchanged.
- Reduces Windows CI flakes where the Core Agent service startup takes longer than short assertion budgets.

## Test plan
- `python3` check: verified all Windows-enabled integration configs have non-top-level `timeout:` values set to `60s`
- `git diff --check`
- `cargo run --bin panoramic -- list -d test/integration/cases`
- Commit hook checks, including formatting, Clippy, license/advisory checks, Vale, and API docs build

## Notes
- Investigated GitLab job 1763487876: `adp-cmd-port` failed because the first `log_contains` assertion had a 10s timeout while ADP was still retrying the configured `https://127.0.0.1:7777/` endpoint before the Windows Datadog Agent service had finished starting.
- The Windows integration job should provide final end-to-end validation.


Co-authored-by: toby.lawrence <toby.lawrence@datadoghq.com>

Author: thieman

test/integration/cases/adp-cmd-port/config.yaml

@@ -31,22 +31,22 @@ assertions:
   # ADP should reach out for config from the core agent on the correct port.
   - type: log_contains
     pattern: "Waiting for initial configuration from Datadog Agent"
-    timeout: 10s
+    timeout: 60s
   # The core agent should start its CMD API server on the non-default port.
   - type: log_contains
     pattern: "Started HTTP server 'CMD API Server' on 127.0.0.1:7777"
-    timeout: 15s
+    timeout: 60s
   # ADP should successfully register with the core agent on that port.
   - type: log_contains
     pattern: "Successfully registered with the Datadog Agent."
-    timeout: 15s
+    timeout: 60s
   # ADP should become healthy and stay up.
   - parallel:
       - type: process_stable_for
         duration: 10s
       - type: log_contains
         pattern: "Topology healthy"
-        timeout: 10s
+        timeout: 60s
       - type: log_not_contains
         pattern: "panic|PANIC"
         regex: true

test/integration/cases/adp-config-check-exit/config.yaml

@@ -25,13 +25,13 @@ env:
 assertions:
   - type: log_contains
     pattern: "Unsupported configuration key with non-default value"
-    timeout: 30s
+    timeout: 60s
   - type: log_contains
     pattern: "incompatible configuration detected"
-    timeout: 30s
+    timeout: 60s
   # Verify ADP actually exited (not just logged the error and continued). On docker this
   # observes the s6 supervisor's exit log; on mac it observes the process exit code
   # directly. Expected code is 1 because the high-severity check returns a non-zero status.
   - type: adp_exits_with
     expected_code: 1
-    timeout: 30s
+    timeout: 60s

test/integration/cases/adp-config-check-warn/config.yaml

@@ -23,7 +23,7 @@ assertions:
   - type: log_contains
     pattern: 'key:"dogstatsd_telemetry_enabled_listener_id" | Unsupported configuration key. Proceeding.'
     regex: true
-    timeout: 30s
+    timeout: 60s
   - parallel:
       - type: process_stable_for
         duration: 10s

test/integration/cases/adp-config-stream/config.yaml

@@ -20,14 +20,14 @@ assertions:
   # Make sure we initially see ADP try to reach out to the Core Agent for its configuration.
   - type: log_contains
     pattern: "Waiting for initial configuration from Datadog Agent"
-    timeout: 10s
+    timeout: 60s
   # Make sure the process becomes healthy, and stays up without errors, for ~10 seconds after.
   - parallel:
       - type: process_stable_for
         duration: 10s
       - type: log_contains
         pattern: "Topology healthy"
-        timeout: 10s
+        timeout: 60s
       - type: log_not_contains
         pattern: "Error while reading config event stream"
         during: 10s

test/integration/cases/adp-disabled-exit/config.yaml

@@ -15,4 +15,4 @@ assertions:
   # ADP should log that it's not enabled and exit.
   - type: log_contains
     pattern: "Agent Data Plane is not enabled. Exiting."
-    timeout: 15s
+    timeout: 60s

test/integration/cases/adp-logging-windows-default-path/config.yaml

@@ -18,8 +18,8 @@ container:
 assertions:
   - type: log_contains
     pattern: "Initial configuration received."
-    timeout: 30s
+    timeout: 60s
   - type: file_contains
     path: "C:\\ProgramData\\Datadog\\logs\\agent-data-plane.log"
     pattern: "DATAPLANE"
-    timeout: 30s
+    timeout: 60s

test/integration/cases/adp-logging-windows-ignores-core-agent-log-file/config.yaml

@@ -20,12 +20,12 @@ container:
 assertions:
   - type: log_contains
     pattern: "Initial configuration received."
-    timeout: 30s
+    timeout: 60s
   - type: file_contains
     path: "C:\\adp\\adp-ignores-core-agent-log-file.log"
     pattern: "DATAPLANE"
-    timeout: 30s
+    timeout: 60s
   - type: file_contains
     path: "C:\\adp\\coreagent-only.log"
     pattern: "CORE"
-    timeout: 30s
+    timeout: 60s

test/integration/cases/adp-logging-windows-respects-data-plane-log-file/config.yaml

@@ -19,8 +19,8 @@ container:
 assertions:
   - type: log_contains
     pattern: "Initial configuration received."
-    timeout: 30s
+    timeout: 60s
   - type: file_contains
     path: "C:\\adp\\adp-custom.log"
     pattern: "DATAPLANE"
-    timeout: 30s
+    timeout: 60s

test/integration/cases/adp-memory-mode-disabled/config.yaml

@@ -18,7 +18,7 @@ env:
 assertions:
   - type: log_contains
     pattern: "Memory limiting disabled."
-    timeout: 15s
+    timeout: 60s
   - parallel:
       - type: process_stable_for
         duration: 10s

test/integration/cases/adp-memory-mode-permissive-exceeds-limit/config.yaml

@@ -19,7 +19,7 @@ env:
 assertions:
   - type: log_contains
     pattern: "Memory limiting behavior will be best effort."
-    timeout: 15s
+    timeout: 60s
   - parallel:
       - type: process_stable_for
         duration: 10s