[wasm] just fix the crypto logging

[pavelsavara]

This only fixes wrong capture of originalConsole causing the crypto-worker to go to infinite loop when WS are not available.
This doesn't address the problem that forwarding logs to localhost WS in production is bad idea.

Contributes to #72941

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

testing crypto on CI

Author:	pavelsavara
Assignees:	pavelsavara
Labels:	arch-wasm, area-System.Runtime.InteropServices.JavaScript
Milestone:	-

[pavelsavara]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pavelsavara]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[radical]

wasm/AOT failure:

[21:59:52] info: Using random seed for collections: 1205411788
[21:59:52] info: Starting: System.Collections.Tests.dll
[22:01:13] fail: 162349888
[22:01:13] fail: [out of order message from the browser]: http://127.0.0.1:49194/dotnet.js 1880:6 Uncaught
[22:01:13] info: WASM EXIT 1

Having an unhandled exception handler to log the trace, specifically for tests, would be very useful in debugging these random crashes.

[radical]

Can you add a description of the problem, and the fix, in the PR description?

[pavelsavara]

Can you add a description of the problem, and the fix, in the PR description?

In old code:
originalConsoleObj is a reference to console object instance.
the methods in it will be rewritten by subsequent call to console[m] = proxyConsoleMethod and therefore are not original, but the modified methods.

In the new code:

const originalConsole = {
log: console.log,
error: console.error
};

creates new object instance with the copy of references to incoming methods and we will not write to that instance after.
So, we could use the original methods in the rest of the setup_proxy_console.

In my other PR I moved all this code to logging.ts and this PR was just speculative.
I will run one more round of CI tests and close it in favor of #73484 which has the same fix in logging.ts

[radical]

And how did the bug show up in practice?
This earlier description and answer to the above can be added to the PR description so it will be in the commit message.

[pavelsavara]

in practice this will run infinite loop and crash the browser as Simon described here #72941