Abort pending tasks with ObjectDisposedException

[pepone]

Fix #3990

.NET 9 updated QUIC implementation to cancel pending task with ODE, when the listener or connection are disposed. This PR updates the failing tests and align Slic with the new QUIC behavior.

[pepone]

I updated Tcp/Coloc listeners to do the same. Alternatively we can move this to Slic and don't update Tcp/Coloc behavior.

[pepone]

Changes required to build conformance tests with .NET9

[pepone]

We just test the new behavior with .NET 9 and greater.

[bernardnormier]

I am surprised there is no change to the Ice/IceRpc ProtocolConnection code that calls these transport APIs.

Even if this code already handles ObjectDisposedException / IceRpcError.OperationAborted the same way, it would make sense to remove the OperationAborted handling from IceProtocolConnection (since no QUIC/Slic for the ice protocol) and add a comment to the IceRpcProtocolConnection code (keep OperationAborted for .NET 8 QUIC support?).

[externl]

Looks good to me!

[pepone]

I am surprised there is no change to the Ice/IceRpc ProtocolConnection code that calls these transport APIs.

I have updated the server code to expect an ObjectDisposedException instead of an IceRpcException(OperationAborted) when calling the AcceptAsync listener operation.

Regarding the IceRpcProtocolConnection, it's unaffected by the changes to CreateStreamAsync and AcceptStreamAsync. In this case, when the connection is disposed, it cancels the cancellation token passed to these operations before disposing of the transport connection. As a result, both CreateStreamAsync and AcceptStreamAsync will still fail with the expected OperationCanceledException. Therefore, the code doesn't need to handle neither IceRpcException(OperationAborted) nor ObjectDisposedException.

Lastly, the IceProtocolConnection does not use any of the updated APIs.

[bernardnormier]

Regarding the IceRpcProtocolConnection, it's unaffected by the changes to CreateStreamAsync and AcceptStreamAsync. In this case, when the connection is disposed, it cancels the cancellation token passed to these operations before disposing of the transport connection

Do you mean it cancels the CTS they use and then waits for these tasks to complete before disposing the connection?

[bernardnormier]

You can simplify - maybe exception is IceRpcException or AuthenticationException?

[pepone]

This additional fix is to ensure QUIC and Slic behave the same. CreateStreamAsync throw OperationCanceledException if ODE is received and task is already canceled.

[pepone]

Do you mean it cancels the CTS they use and then waits for these tasks to complete before disposing the connection?

I think there was a difference here with Slic and QUIC in CreateStreamAsync.

If you cancel the cancellation token passed to CreateStreamAsync and then dispose the connection.

Slic throws OperationCancelledException, Quic throws ObjectDisposedException, I fixed Quic connection to behave as Slic adding:

        catch (ObjectDisposedException)
        {
            cancellationToken.ThrowIfCancellationRequested();
            throw;
        }