Windows connect test flaking with all pipe instances are busy

[jsturtevant]

          > @jsturtevant any thoughts on

---- synchronous::publisher::tests::test_connect stdout ----
thread 'synchronous::publisher::tests::test_connect' panicked at 'called `Result::unwrap()` on an `Err` value: Ttrpc(Windows(231))', crates\shim\src\synchronous\publisher.rs:159:50
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

231 is all pipe instances are busy might be a flaky test. Has is shown up in other PR's? I will create an issue and see if I can reproduce.

Originally posted by @jsturtevant in #152 (comment)

[jsturtevant]

this looks to be a flake as the nightly job is passing: https://github.com/containerd/rust-extensions/actions/runs/5570559244

[jsturtevant]

saw this again here: https://github.com/containerd/rust-extensions/actions/runs/5834889652/job/15825376914?pr=177

[jsturtevant]

saw this today: https://github.com/containerd/rust-extensions/actions/runs/6318762369/job/17158455962?pr=181

I've tried reproducing locally with the following but not having any luck.

for ($i=0; $i -le 100; $i++) { cargo test -p containerd-shim }