integration-cli: retry Windows npipe connect EOF in TestRunTwoConcurrentContainers - #53395

Summary

Hardens flaky TestDockerCLIRunSuite/TestRunTwoConcurrentContainers on Windows.

Failure

On windows-2022 CI, one of two concurrent docker run calls intermittently fails with:

docker: error during connect: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.44/containers/create": EOF.

Exit code 125 after ~60s. Same class of Windows named-pipe transport flake as #49348 / #53269 (concurrent engine API traffic over //./pipe/docker_engine under CI load).

Fix

Keep the concurrent launches (that is what this test covers). Retry each docker run up to 3 times only when the error matches the transient connect EOF pattern (error during connect + EOF). All other failures still fail the test immediately.

Residual risk

• This does not fix a possible daemon/snapshotter root cause (e.g. slow concurrent create / VHD+boltdb contention on WCOW that can idle the npipe until EOF).
• If every attempt hangs ~60s before EOF, the test can still be slow or fail after 3 attempts.
• A create that actually succeeded server-side while the client saw EOF could leave an extra anonymous container; suite teardown cleans those up.

Fixes #53343

Test plan

• Localized change to existing integration-cli test only
• Windows CI: TestDockerCLIRunSuite/TestRunTwoConcurrentContainers
• Confirm Linux path unchanged in behavior (retries only on connect EOF, which is Windows-specific in practice)