Subsequent call to StreamShutdown(ABORT_RECEIVE) seems to overwrite the first passed error code

[CarnaViire]

As per dotnet/runtime#55724 (comment) I found out that if I abort receive on the stream the second time, my error code might end up overwritten.

The test calls AbortRead(1234) on msquic stream and then the stream gets disposed, and that triggers AbortRead(0xffffffff) which we expected to be a no-op. The test expects peer to receive the first error code (1234). However, rarely the test can fail with peer receiving wrong (second) error code (0xffffffff=4294967295)

Assert.Equal() Failure
Expected: 1234
Actual:   4294967295