[Named Pipe] Check for pipe broken on WaitConnectionAsync

[JamesNK]

Changes from #46182

I looked up situations that can cause a broken pipe and most sources mention a broken pipe can happen when the other side has disconnected. I'm unsure how that could apply to WaitForConnectionAsync because we're waiting for a client to connect. Perhaps the client can request a connection, then disconnect before WaitForConnectionAsync returns the stream.

No test, as I could not create a situation where a broken pipe exception was thrown.

@simonferquel I added logging because I'm wary of catching an error and continuing without any record of what is happening. If there is a situation where a server keeps getting broken pipes and goes into an infinite loop, there is logging to explain what the server is doing. I'm not sure if that can happen, just being cautious.

[simonferquel]

Logging seem a good idea. On our own reliability tests at Unity (where we have a similar custom Listener implementation), we encounter broken pipes on WaitForConnection under sustained high load (e.g. a few minutes of both CPU and memory high usage).
Also something we do on client-side before connecting, is to use File.Exists("\\\\.\\pipe\\{namedPipeOrUnixSocket}") to check of the server side existence.