bug: noisy janky handling of named pipes on windows

[aconverse]

steps to repro:

1. Install eza on windows
2. start google chrome (makes a lot of pipes)
3. eza "\\.\pipe\"

output:

PS C:\Users\Alex> eza \\.\pipe\
[\\.\pipe\Winsock2\CatalogChangeListener-47c-0: Access is denied. (os error 5)]
[\\.\pipe\Winsock2\CatalogChangeListener-5d8-0: Access is denied. (os error 5)]
[\\.\pipe\Winsock2\CatalogChangeListener-414-0: Access is denied. (os error 5)]
[\\.\pipe\Winsock2\CatalogChangeListener-608-0: Access is denied. (os error 5)]
[\\.\pipe\Winsock2\CatalogChangeListener-aa0-0: Access is denied. (os error 5)]
[\\.\pipe\Winsock2\CatalogChangeListener-bb0-0: Access is denied. (os error 5)]
[\\.\pipe\Winsock2\CatalogChangeListener-c74-0: Access is denied. (os error 5)]
[\\.\pipe\Winsock2\CatalogChangeListener-12d0-0: Access is denied. (os error 5)]
[\\.\pipe\Winsock2\CatalogChangeListener-45c-0: Access is denied. (os error 5)]
[\\.\pipe\PIPE_EVENTROOT\CIMV2SCM EVENT PROVIDER: Access is denied. (os error 5)]
[\\.\pipe\mojo.1680.10752.4253034693678138656: All pipe instances are busy. (os error 231)]
[\\.\pipe\mojo.1680.10752.5839597344748073699: All pipe instances are busy. (os error 231)]
[\\.\pipe\mojo.16220.25164.10780065382346818521: All pipe instances are busy. (os error 231)]
[\\.\pipe\mojo.16220.25164.2985583260185508599: All pipe instances are busy. (os error 231)]
[\\.\pipe\mojo.16220.25164.16553505636731536170: All pipe instances are busy. (os error 231)]
[\\.\pipe\mojo.16220.24152.3047610705277600690: All pipe instances are busy. (os error 231)]
[\\.\pipe\mojo.16220.24152.14334398270879800915: All pipe instances are busy. (os error 231)]
[\\.\pipe\mojo.16220.25164.14697369159919092017: All pipe instances are busy. (os error 231)]
[\\.\pipe\mojo.16220.25164.3699848374063609124: All pipe instances are busy. (os error 231)]
[\\.\pipe\mojo.16220.24152.12038592775478825273: All pipe instances are busy. (os error 231)]
[\\.\pipe\mojo.16220.24152.2801501495616158200: All pipe instances are busy. (os error 231)]
...

Digging in it seems like eza is trying to stat the pipes (confirmed with $Env:EZA_DEBUG = "true") but windows pipes don't seem to have meaningful stat. (see eza -l \\.\pipe\ or Get-ChildItem \\.\pipe\) They have no creation time or modified time. It also seems totally expected that CreateFile (to open the handle) on a busy pipe would fail.

---

• The version of eza being used (eza --version): v0.19.1 [+git]
• The command-line arguments you are using: eza "\\.\pipe\"
• Your shell and terminal: PowerShell 7.4.5 in Windows Terminal 1.21
• Your operating system and hardware platform: Windows 11 22631.4037 x64