[QUIC] Fixed exception type for ConnectionShutdownInitiatedByTransport

[ManickaP]

In case of a shutdown by a transport we would throw QuicOperationAbortedException out of AcceptStreamAsync, which would wrongly imply that it was our side who initiated the connection shutdown.
This is a quick safe fix to make the logic throw QuicConnectionAbortedException instead.

However, we should properly propagate outside the information that it was transport and not the peer who closed the connection --> not closing the original issue.

Fixes #60133

Verified manually, now seeing in Kestrel log:

dbug: Microsoft.AspNetCore.Server.Kestrel.Transport.Quic[5]
      Connection id "0HMCADU0GKLVK" aborted by peer with error code 0.
      System.Net.Quic.QuicConnectionAbortedException: Connection aborted by peer (0).
         at System.Net.Quic.Implementations.MsQuic.MsQuicConnection.AcceptStreamAsync(CancellationToken cancellationToken)
         at System.Net.Quic.QuicConnection.AcceptStreamAsync(CancellationToken cancellationToken)
         at Microsoft.AspNetCore.Server.Kestrel.Transport.Quic.Internal.QuicConnectionContext.AcceptAsync(CancellationToken cancellationToken)
dbug: Microsoft.AspNetCore.Server.Kestrel.Transport.Quic[6]
      Connection id "0HMCADU0GKLVK" aborted by application with error code 0 because: "The client closed the connection.".

cc @JamesNK @CarnaViire

[sebastienros]

After testing, I confirm I can't repro the issue anymore (from an E2E perspective).

[CarnaViire]

Thanks!

[ManickaP]

/backport to release/6.0

[github-actions]

Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1328653526