运行 anyproxy --intercept 时报错 throw er; // Unhandled 'error' even

**Platform** : Windows 11 Home 21H2 X64
**AnyProxy Version**: 4.1.3

运行 anyproxy --intercept 时报错，报错信息如下：

C:\Users\admin>anyproxy --intercept
node:events:504
throw er; // Unhandled 'error' event
^

Error: spawn powershell.exe ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:478:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
at onErrorNT (node:internal/child_process:478:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn powershell.exe',
path: 'powershell.exe',
spawnargs: [
'-ExecutionPolicy',
'Bypass',
'-NoProfile',
'-NoLogo',
'-NoExit',
'-InputFormat',
'Text',
'-Command',
'-'
]
}

Start by locating the `anyproxy --intercept` entry point and the PowerShell child-process invocation, then reproduce the command on Windows 11 with AnyProxy 4.1.3. Done means the command no longer fails with `spawn powershell.exe ENOENT` and its intercept behavior can start normally.

Written by the indexing model from the issue text.