Support Windows NamedPipe's in Kestrel

[mconnew]

Is your feature request related to a problem? Please describe.

CoreWCF needs to be able to accept connections on Windows named pipes to accept connections from existing .NET Framework clients.

Describe the solution you'd like

CoreWCF needs to support creating a listening pipe on both local and global namespaces. We also need to be able to modify the ACL on the named pipe (PipeStream.GetAccessControl/SetAccessControl).

---

Update 2022/12/22 @JamesNK

Initial commit - #44426

Work still to do:

• Add option to validate first connection. Waiting on [API Proposal]: Add PipeOptions.FirstPipeInstance enum value runtime#76984
• Perf and stress testing
• End-to-end testing with gRPC
• End-to-end testing with WCF? cc @mconnew
• Documentation
• Security guidance

[blowdart]

Tagging @danmoseley because this fits into the email discussion around permissions apis that will vary by platform

[mconnew]

@blowdart, this will only be used by CoreWCF on Windows as we have a convoluted mechanism which needs to be followed to be compatible with existing WCF clients. But as WCF only uses this for localhost communication, it doesn't need to be supported on Linux. We can use the datagram sockets on Linux instead as there is no existing mechanism which we would need to be compatible with.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.