[Wasm][AOT] Exceptions in Full AOT should provide the native stack frames

[jeromelaban]

Description

When an exception is raised when running in FullAOT (or mixed), exception raised do not provide managed frames (stack walking is not available in WebAssembly).

Yet, using new Error().stack provides the native WebAssembly frames, which can be very useful to troubleshoot and pinpoint issues.

Adding the native frames in the Exception.Data dictionary could be an interesting location to provide this information, and avoid altering existing behaviors (e.g. inner exception).

Configuration

WebAssembly.

Regression?

No

Other information

[ghost]

Tagging subscribers to this area: @CoffeeFlux
See info in area-owners.md if you want to be subscribed.

---

Issue meta data

Issue content:
	<!--This is just a template - feel free to delete any and all of it and replace as appropriate.--> Description When an exception is raised when running in FullAOT (or mixed), exception raised do not provide managed frames (stack walking is not available in WebAssembly). Yet, using new Error().stack provides the native WebAssembly frames, which can be very useful to troubleshoot and pinpoint issues. Adding the native frames in the Exception.Data dictionary could be an interesting location to provide this information, and avoid altering existing behaviors (e.g. inner exception). Configuration WebAssembly. Regression? No Other information </td>
Issue author:		jeromelaban
Assignees:	-
Labels:	`arch-wasm`, `area-VM-meta-mono` </td>
Milestone:	-

[jeromelaban]

Fixed by #44628