chore(deps): update test-tooling (9.5)

[elastic-renovate-prod]

This PR contains the following updates:

Package	Type	Update	Change
github.com/moby/moby/api	require	minor	v1.55.0 → v1.56.0
github.com/stretchr/testify	require	patch	v1.12.0 → v1.12.1

---

Release Notes

stretchr/testify (github.com/stretchr/testify)

v1.12.1

Compare Source

This is the first release which has the minimum dependencies practical in testify v1. The last remaining dependencies are github.com/stretchr/objx which itself has no dependencies, and go.yaml.in/yaml/v3. Removing objx would require v2, it cannot be vendored. Removing YAML would require vendoring the yaml library, which would do more harm than good. It's better to become aware of vulnerabilities in the official yaml package than to attempt to maintain our own.

What's Changed

• Change yaml library to go.yaml.in/yaml/v3 by @​harryzcy in #​1935
• change yaml library to go.yaml.in/yaml/v3 by @​boekkooi-impossiblecloud in #​1772

New Contributors

• @​harryzcy made their first contribution in #​1935
• @​boekkooi-impossiblecloud made their first contribution in #​1772

Full Changelog: stretchr/testify@v1.12.0...v1.12.1

What's Changed

• Change yaml library to go.yaml.in/yaml/v3 by @​harryzcy in #​1935
• change yaml library to go.yaml.in/yaml/v3 by @​boekkooi-impossiblecloud in #​1772

New Contributors

• @​harryzcy made their first contribution in #​1935
• @​boekkooi-impossiblecloud made their first contribution in #​1772

Full Changelog: stretchr/testify@v1.12.0...v1.12.1

---

Configuration

📅 Schedule: Branch creation - "on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[github-actions]

TL;DR

Buildkite failed in E2E due to two fast-failing tests in TestStandAloneRunningSuite: TestAgentGracefulForceUnenroll and TestOpAMPWithEDOTCollector. Given this PR only bumps github.com/stretchr/testify from v1.12.0 to v1.12.1, this looks most consistent with test/environment flakiness rather than a dependency-induced code regression.

Remediation

• Re-run the failing Buildkite build first to confirm whether this is transient (https://buildkite.com/elastic/fleet-server/builds/16535).
• If it reproduces, run only the failing E2E tests with focused logging and compare behavior before/after the dependency bump:
  • mage test:e2e TEST_RUN='TestStandAloneRunningSuite/(TestAgentGracefulForceUnenroll|TestOpAMPWithEDOTCollector)'
  • Capture Fleet Server + test harness logs around those two tests to isolate the failing assertion/site.

Investigation details

Root Cause

The failing job is .buildkite/scripts/e2e_test.sh with package-level failure in github.com/elastic/fleet-server/testing/e2e, and exactly two subtests marked failed:

• testing/e2e: TestStandAloneRunningSuite/TestAgentGracefulForceUnenroll
• testing/e2e: TestStandAloneRunningSuite/TestOpAMPWithEDOTCollector

No panic/compile/type/dependency-resolution error appears in the captured log. The visible Toxiproxy warnings (use of closed network connection) occur in resilience tests and are expected noise in those scenarios, not a direct failure signal.

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/16535
• Job/step: E2E Test (.buildkite/scripts/e2e_test.sh)
• Key log excerpt:
  • --- FAIL: TestStandAloneRunningSuite (411.04s)
  • --- FAIL: TestStandAloneRunningSuite/TestAgentGracefulForceUnenroll (0.04s)
  • --- FAIL: TestStandAloneRunningSuite/TestOpAMPWithEDOTCollector (0.01s)
  • FAIL github.com/elastic/fleet-server/testing/e2e 951.286s
• PR delta is dependency-only (go.mod, go.sum, NOTICE.txt, NOTICE-fips.txt) for github.com/stretchr/testify v1.12.0 -> v1.12.1, with no direct runtime code changes.

Verification

• Not run locally in this environment (detective workflow is read-only and relies on provided Buildkite artifacts/logs).

Follow-up

If this repeats, please attach expanded logs for those two failing tests (assertion text/stack trace). With only the truncated artifact provided, the exact failing assertion line cannot yet be pinned.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.