In case of SHUTDOWN_INITIATED_BY_TRANSPORT we now get transport level error code, but we don't use it.

We also get it in SHUTDOWN_COMPLETE.ConnectionShutdown case where we would throw the same exception as in SHUTDOWN_INITIATED_BY_TRANSPORT in ideal case.

There might still be necessity to expand msquic data to avoid holding stream -> connection link to solve this properly.

https://www.rfc-editor.org/rfc/rfc9000.html#name-transport-error-codes