[QUIC] Finalize QUIC stream abort model

[scalablecory]

QUIC supports aborting the read or write side of a stream independently from the other side of the stream.

We should determine how to allow a user to do an "abortive dispose" such that all pending I/Os in both directions are aborted.

runtime/src/libraries/System.Net.Quic/src/System/Net/Quic/Implementations/MsQuic/MsQuicStream.cs

Lines 313 to 315 in 65587ba

	// TODO do we want this to be a synchronization mechanism to cancel a pending read
	// If so, we need to complete the read here as well.
	internal override void AbortRead(long errorCode)

runtime/src/libraries/System.Net.Quic/src/System/Net/Quic/Implementations/MsQuic/MsQuicStream.cs

Lines 364 to 381 in 65587ba

	// TODO do anything to stop writes?
	using CancellationTokenRegistration registration = cancellationToken.Register(() =>
	{
	bool shouldComplete = false;
	lock (_sync)
	{
	if (_shutdownState == ShutdownWriteState.None)
	{
	_shutdownState = ShutdownWriteState.Canceled;
	shouldComplete = true;
	}
	}
	if (shouldComplete)
	{
	_shutdownWriteResettableCompletionSource.CompleteException(new OperationCanceledException("Shutdown was canceled"));
	}
	});

[geoffkizer]

Isn't this captured already by #756? What's not captured there?

[ManickaP]

Should we close this as a dupe of #756?

[CarnaViire]

I believe we wanted to split #756 into several issues instead #756 (comment)

[scalablecory]

Triage: we think the abort APIs will look like this:

class QuicStream
{
    // abortive -- causing any unsent data to be discarded.
    // one direction can be aborted while leaving the other direction open.
    // should cause any outstanding ops to throw StreamAbortedException.
    public void Abort(long errorCode, QuicAbortDirection direction = QuicAbortDirection.Both);
}

[Flags]
enum QuicAbortDirection
{
   Read = 1,
   Write = 2,
   Both = 3
}

[ManickaP]

Coverd by #756