Investigate SpawnBrowserAsync issue by adding debugging.

[ilonatommy]

When investigating #107771, more debugging would be useful. What's more, switching it on in the PR aiming to fix the issue revealed 0 hit count. It is not a proper fix but it's probable that it will decrease the hit count on main and can be treated as a temporary measure.

[pavelsavara]

Does that increase logging ? Could you please attach example of the log it produces ?
Are we able to capture the log from CI too ?

[ilonatommy]

Does that increase logging ? Could you please attach example of the log it produces ? Are we able to capture the log from CI too ?

Here we have a log with only pw:browser, without the protocol: https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-107865-merge-17e567dc36914e5798/Workloads-NoWebcil-ST-Wasm.Build.Tests.WasmTemplateTests/1/console.9c7b17ec.log?helixlogtype=result.

Adding protocol as well was suggested by Playwright team.

Edit:
here we have a log with both: https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-108440-merge-224a492c411e448eae/Workloads-ST-Wasm.Build.NativeRebuild.Tests.FlagsChangeRebuildTests/1/console.05ce4e89.log?helixlogtype=result
I don't see any lines added by pw:protocol or pw:browser in this PR. It might be caused by old pw used here, so merging with main. Thanks for asking about that!

[ilonatommy]

Tests that failed and use PW have truncated logs, e.g. see:
https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-108440-merge-bab20210b888447b9f/Workloads-ST-Wasm.Build.Tests.IcuTests/1/console.13adc915.log?helixlogtype=result

Other tests that use PW but passed are in a similar situation:
https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-108440-merge-bab20210b888447b9f/Workloads-ST-Wasm.Build.Tests.TestAppScenarios.LazyLoadingTests/1/console.de923424.log?helixlogtype=result

Conclusion: this PR does not help in debugging. Closing.