Fix WASM debugger breakpoints not hitting after Terser 5.39+.

[ilonatommy]

Terser 5.39 introduced an optimization that removes console.assert(true, ...) as "unnecessary" https://github.com/terser/terser/blob/master/CHANGELOG.md#v5390.

In runtime we are counting on the assert to keep base64String:

runtime/src/mono/browser/runtime/debug.ts

Line 37 in 1af7e1a

//keep this console.assert, otherwise optimization will remove the assignments

The assert removal caused the base64String to be optimized away, breaking the BrowserDebugProxy's ability to read debugger agent info from the paused scope.

This affects net11 debugging, net10 works correctly.

This PR replaces true with !!Date.now() which Terser cannot statically evaluate.

[dotnet-policy-service]

Tagging subscribers to this area: @steveisok, @thaystg, @dotnet/dotnet-diag
See info in area-owners.md if you want to be subscribed.

[Copilot]

Pull request overview

This PR fixes a critical bug where WASM debugger breakpoints stopped working after Terser 5.39+ was introduced. Terser 5.39 added an optimization that removes console.assert(true, ...) statements as "unnecessary", which broke the debugger proxy's ability to read variables from paused scopes. The fix replaces the static true value with !!Date.now(), which evaluates to true at runtime but cannot be statically analyzed by Terser.

Changes:

• Updated two console.assert calls to use !!Date.now() instead of true to prevent Terser optimization
• Added clear explanatory comments describing why the change was necessary and how the workaround works