stat.isFIFO() is wrongly marked as always false on Windows, even when piping into a node process

### Version v22.14.0 ### Platform ```text Microsoft Windows NT 10.0.26120.0 x64 [although this is on ARM64] ``` ### Subsystem _No response_ ### What steps will reproduce the bug? Running `echo '{}' | node -e 'console.log(require("fs").fstatSync(0).mode)'` in PowerShell (as cmd doesn't seem to support pipes via the usual syntax) returns 4096, and checking `fs.constants`, `S_IFIFO` is set to `4096`. ### How often does it reproduce? Is there a required condition? Seems to be all the time on Windows when you try to pipe something in, which is due to a (I assume legacy?) check here: https://github.com/nodejs/node/blob/c3b6f949748b49ef25b0239bd4582d29976fdbad/lib/internal/fs/utils.js#L538-L541 ### What is the expected behavior? Why is that the expected behavior? On Windows, `stat.isFIFO()` should correctly handle pipes and `stat.isFIFO()` should correctly return `true` when piped in ### What do you see instead? `stat.isFIFO()` always returns false on Windows, even if the mode has the flag set ### Additional information I would love to submit a PR to fix this, but I am not sure if those checks are there for a reason or for legacy purposes (it seems that at least the S_ISFIFO is now exposed but it wasn't before [?]), and if it can be edited safely.