[Feature Request] Catch Exception from calling EndInvoke and recommend/dynamically reducing Threads

This is a feature request to add dynamic Thread reduction when `EndInvoke` function causes any kind of exception. Otherwise, exit early with a message to recommend for the -Threads parameter to be used.

Specifically this error that I ran into because the default 500 threads is too high for my virtual lab:
```
Exception calling "EndInvoke" with "1" argument(s): "Thread failed to start."
At C:\temp\IPv4PortScan.ps1:260 char:13
+ $Job_Result = $Job.Pipe.EndInvoke($Job.Result)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ThreadStartException

Exception calling "EndInvoke" with "1" argument(s): "Thread is running or terminated; it cannot restart."
```

從 C:\temp\IPv4PortScan.ps1 的第 260 行附近開始，查看 $Job.Pipe.EndInvoke($Job.Result) 引發所回報例外的位置，並追蹤 -Threads 參數如何控制工作建立。確定失敗應如何減少執行緒數量或產生提前建議，然後根據顯示的兩個 EndInvoke 錯誤驗證行為。

由索引模型根據 Issue 內容生成。