[Bug?]: support for -S in env shebang

[npenin]

Self-service

• I'd be willing to implement a fix

Describe the bug

when using the -S parameter on env shebang line, the generated shim files are completely messed up

To reproduce

#!/usr/bin/env -S node --enable-source-maps
console.log('hello world')

Environment

System:
    OS: Windows 11 10.0.22631
    CPU: (32) x64 13th Gen Intel(R) Core(TM) i9-13900K
  Binaries:
    Node: 22.2.0 - ~\AppData\Local\Temp\xfs-d216ad6d\node.CMD
    Yarn: 4.1.1 - ~\AppData\Local\Temp\xfs-d216ad6d\yarn.CMD
    npm: 10.7.0 - C:\Program Files\nodejs\npm.CMD

Additional context

it is true for both generated shims on windows: shim and shim.cmd

[npenin]

apparently should have been covered by pnpm/cmd-shim@218d337