In PSScript and PSAdapter, if TryDequeue fails, we just return

[SteveL-MSFT]

PR Summary

Something is causing a hang. According to the docs TryDequeue should only fail if empty, but perhaps there's some unknown interaction resulting in TryDequeue failing, but IsEmpty reports not, so change is to return if TryDequeue fails.

PR Context

Fix #1609

[Copilot]

Pull request overview

This PR mitigates a potential hang in the PowerShellScript resource and the PowerShell adapter by avoiding an infinite loop when ConcurrentQueue.TryDequeue() unexpectedly returns false while IsEmpty indicates the queue is not empty (likely due to concurrency timing).

Changes:

• Add an early-return guard in Write-TraceQueue() when TryDequeue() fails (PSScript resource).
• Add the same early-return guard in Write-TraceQueue() for the PowerShell adapter.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
resources/PSScript/psscript.ps1	Prevents Write-TraceQueue() from potentially looping forever if TryDequeue() fails despite IsEmpty being false.
adapters/powershell/psDscAdapter/powershell.resource.ps1	Applies the same protection to adapter-side trace draining to avoid hangs in adapter execution.

[SteveL-MSFT]

Abandoning this change, it's causing test failures.