[release/7.0-rc2] [wasm] fix missing managed stack trace on managed exceptions marshaled to JS

[pavelsavara]

Backport of #75678 to release/7.0-rc2

/cc @pavelsavara@kg

Customer Impact

Fixes stack trace on managed stack trace, which was marshaled as JavaScript Error. The main impact is that unhanded exceptions from [JSExport] will be easier to diagnose than without the managed stack.

Testing

I done:

• New unit tests
• run unit tests on Chrome, FireFox and NodeJS
• run full CI test suite for wasm on main branch
• manual test

Risk

Low
There is probably no production code which would rely on this yet, as the [JSExport] interop is new in .Net 7.
The stack traces are targeted at human developer and relying on exact text of the stack trace is considered bad practice.

[ghost]

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

Issue Details

---

Backport of #75678 to release/7.0-rc2

/cc @pavelsavara@kg

Customer Impact

Fixes stack trace on managed stack trace, which was marshaled as JavaScript Error. The main impact is that unhanded exceptions from [JSExport] will be easier to diagnose than without the managed stack.

Testing

I done:

• New unit tests
• run unit tests on Chrome, FireFox and NodeJS
• run full CI test suite for wasm on main branch
• manual test

Risk

Low
There is probably no production code which would rely on this yet, as the [JSExport] interop is new in .Net 7.
The stack traces are targeted at human developer and relying on exact text of the stack trace is considered bad practice.

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

[pavelsavara]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pavelsavara]

The issue is Failed to resolve SDK 'Microsoft.Build.NoTargets/3.5.0'

[carlossanlop]

Needs Tactics approval. @pavelsavara please send the email to Tactics if you haven't yet.

[pavelsavara]

The CI failures are unrelated.

[radical]

Approving based on approvals on the original PR for main.

[radical]

The wasm/runtimeTests failures are unrelated.

[carlossanlop]

And the failure to resolve Microsoft.Build.NoTargets/3.5.0 is this existing issue, which is a duplicate of this more generic one.

Signed off, approved, ready to merge.