Increase stack size for PowerShell 5 (#1797)

Sets the `Thread` max stack size to use the same value that is normally used in console host. This gives PowerShell code more room for execution, so recursive calls, or calls that are wrapped in Pester (which itself is stack-hungry), won't fail with: 

```
System.Management.Automation.ScriptCallDepthException: The script failed due to call depth overflow.
```

Fixes: PowerShell/vscode-powershell#3962

Author: nohwnd

src/PowerShellEditorServices/Services/PowerShell/Host/PsesInternalHost.cs

@@ -112,7 +112,16 @@ public PsesInternalHost(
             _runspaceStack = new Stack<RunspaceFrame>();
             _cancellationContext = new CancellationContext();
 
-            _pipelineThread = new Thread(Run)
+            // Default stack size on .NET Framework is 524288 (512KB) (as reported by GetProcessDefaultStackSize)
+            // this leaves very little room in the stack. Windows PowerShell internally sets the value based on 
+            // PipelineMaxStackSizeMB as seen here: https://github.com/PowerShell/PowerShell/issues/1187, 
+            // which has default of 10 and multiplies that by 1_000_000, so the default stack size is
+            // 10_000_000 (~10MB) when starting in normal console host. 
+            //
+            // For PS7 the value is ignored by .NET because settings the stack size is not supported, but we can 
+            // still provide 0, which means fallback to the default in both .NET and .NET Framework.
+            int maxStackSize = VersionUtils.IsPS5 ? 10_000_000 : 0;
+            _pipelineThread = new Thread(Run, maxStackSize)
             {
                 Name = "PSES Pipeline Execution Thread",
             };