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 が実行されないことを検証します。動作が確認されるか、必要な改良点が文書化されテストされれば完了です。