[Feature Request]: Support windows named pipes

[Named pipes](https://learn.microsoft.com/en-us/windows/win32/ipc/named-pipes) are already something supported in [tokio](https://docs.rs/tokio/latest/tokio/net/windows/named_pipe/index.html).

This would be useful in windows systems in situations where it would preferable to not use a TCP socket when traffic is across the same machine in request response model.

Start with the Tokio Windows named-pipe documentation linked in the issue, then inspect tarpc's current transport entry points and how request-response traffic is supported. Done means tarpc can use Windows named pipes for same-machine request-response communication without relying on a TCP socket.

Written by the indexing model from the issue text.