Refactor transport tests to better report pattern match failures

[LaurentRDC]

Many tests from network-transport-tests use partial pattern matches to test expectations. Unfortunately, this leads to hard-to-debug problems.

This PR adds functionality to network-transport-tests to express expectations in a way that makes it easier to report problems. See below for an example.

Before:

$ cabal test network-transport-quic
network-transport-quic
...
closeEndPoint: FAIL (0.55s)
Exception: user error (Pattern match failure in 'do' block at src/Network/Transport/Tests.hs:677:7-28)
Trace:
0 ErrorEvent (TransportError (EventConnectionLost 127.0.0.1:50190:3) "Connection reset")
1 Received 12884901888 ["ping"]
2 ConnectionOpened 12884901888 ReliableOrdered 127.0.0.1:50190:3
3 "127.0.0.1:50190:3"
[3 retries, 0 μs delay]
Use -p '/closeEndPoint/' to rerun this test only.
...

Now:

$ cabal test network-transport-quic
network-transport-quic
...
closeEndPoint: FAIL (0.53s)
Exception: user error (testCloseEndPoint (server, 2): ConnectionClosed: expected ConnectionClosed 12884901888, got ErrorEvent (TransportError (EventConnectionLost 127.0.0.1:58512:3) "Connection reset")
CallStack (from HasCallStack):
expectEq, called at src/Network/Transport/Tests.hs:712:7 in network-transport-tests-0.3.4-inplace:Network.Transport.Tests)
Trace:
0 ErrorEvent (TransportError (EventConnectionLost 127.0.0.1:58512:3) "Connection reset")
1 Received 12884901888 ["ping"]
2 (12884901888,ReliableOrdered,"127.0.0.1:58512:3")
3 "127.0.0.1:58512:3"
[3 retries, 0 μs delay]
Use -p '/closeEndPoint/' to rerun this test only.
...

[LaurentRDC]

I think I have a fix for the QUIC flaky tests, but this is going to be in a separate PR