[Work Item] Debug Logging in Multi Thread and Remote Server

[dpaulson45]

Describe the work
In order to have proper debug logging occurring, we still need to have our Write-Verbose, Write-Host, and other various default cmdlets that we override to still do a logging functionality, even when we are doing a multi-threaded or remote execution.

Need to come up with a way to pull out this information and properly display it as we would normally do in a single session.

Additional Context
This was partly done within Exchange Log Collector, but there should be a better way to handle this.

[dpaulson45]

https://devblogs.microsoft.com/scripting/weekend-scripter-welcome-to-the-powershell-information-stream/

https://devblogs.microsoft.com/scripting/understanding-streams-redirection-and-write-host-in-powershell/

After digging into this, now understand why Exchange Log Collector was done the way it is handled. The best option for when we are using Write-Host and Write-Verbose to log out that information.

Currently don't see a better option than to use the method of Add-ScriptBlockInjection to our script block that we want to have and then possibly create a better option for the PipelineFunctions.ps1 to handle us putting Write-Verbose and Write-Host on the pipeline to be returned.

When putting this in the Shared, need to make sure that we have a good Pester test for this action as well.