Describe the bug

Might be related to #1582, but might not.

In the latest main CI run, on Windows OpenSSL, we hit the following failure:

[ RUN      ] ParameterValidation.ValidateConnection
D:\a\1\msquic\src\test\lib\ApiTest.cpp(492): error: Peer never signaled connected event
[  FAILED  ] ParameterValidation.ValidateConnection (11589 ms)

This corresponds to this code:

Tokio's automatic cooperative task yielding feature can cause abruptly prevent a task from making further progress. A very busy connection driver might as a result end up failing to fairly serve transmits or timeouts, resulting in bad behavior (e.g. spurious timeouts or congestion window reduction) under heavy load.

Ideally tokio will expose some too

file echo_client.c, line:121 st_h->read_stdin_ev = event_new(prog_eb(st_h->client_ctx->prog),
STDIN_FILENO, EV_READ, read_stdin, st_h);

I've changed my local version to:

public QuicStreamContext CreateStream(ulong streamId = 1, StreamType streamType = StreamType.ClientBidirectional);

in order to keep the compatibility.