Verify the main runspace reset method in the PSES pipeline thread consumer

We have a kind of primitive stab at a method to clean up a faulty runspace state in the PSES pipeline thread consumer here:

https://github.com/PowerShell/PowerShellEditorServices/blob/9fd0dfa58438a9ba2b2d3cdfe22cd9cad5df70b0/src/PowerShellEditorServices/Services/PowerShell/Host/PsesInternalHost.cs#L784-L826

We need to induce a fault and see if this works as expected, as well as ensure it doesn't run at other times...

My suspicion is that it will need some refinement and could have some significant bugs in it. But it's currently a corner case and a worse-case scenario handler anyway (if it didn't exist, we are essentially crashed).

So we need to investigate this and see how we can improve:

• detection of bad runspace state
• restoration of good runspace state
• how our threading mechanisms work in this scenario...

先从 src/PowerShellEditorServices/Services/PowerShell/Host/PsesInternalHost.cs 的第 784–826 行附近开始，然后跟踪 pipeline 线程消费者及其 runspace 状态处理。诱发 issue 中描述的错误 runspace 条件，并验证检测、恢复，以及 reset 不会在正常运行期间执行；当行为得到确认，或所需的改进已记录并经过测试时，即表示完成。