Diagnostics and fix for pipeline test failures by JohnMcPMS · Pull Request #5975 · microsoft/winget-cli

Change

Add more data to try and get to the bottom of the test failures in the pipeline.

Most importantly adds an extensive tracing that wraps the failing task to hopefully get more details.

Also adds the PID to the startup logging and a message to indicate that the server is exiting due to its event being signaled. These won't actually be used in the pipeline right now, as the failure is happening the in GA PS/COM interaction. But they are helpful for diagnosing issues anyway.

Microsoft Reviewers: Open in CodeFlow