Desktop App dotnet 6.0 client Add wcf service reference wizard does not autogenerate client proxies correctly for netnamedpipebinding

**Describe the bug**
Desktop app dotnet 6.0 client Add wcf service reference wizard does not autogenerate client proxies correctly for netnamedpipebinding also netnamedpipe nuget reference does not get added.

**To Reproduce**
Steps to reproduce the behavior:
Create service with netnamedpipebinding only try to use in dotnet 6 client by adding service reference.
Please find below sample project modified server exe need to be run as administrator.
[SampleNetPipeServiceReference.zip](https://github.com/dotnet/wcf/files/12365543/SampleNetPipeServiceReference.zip)

**Expected behavior**
Similar to older netframework full client proxies should get generated for dotnet 6.0 for named pipe binding client, should not have build issues. all nuget needed references should get added.

**Work around earlier suggested in another netnamedpipe issue**
To use TCP binding and then change auotgenerated code manually to netnamedpipe binding