[wasm] .NET WebAssembly profiling and memory diagnostics

[lambdageek]

Moved remaining goals to #76316

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

Issue Details

---

Basics:

• [wasm-ep] Minimal diagnostic tracing configuration and sample #69158
  This adds support for using the JS console to create an EventPipe session with the default providers and to collect a trace in-memory to the Emscripten VFS and to egress it to a JavaScript Blob object (which can then be downloaded).
• Add support for specifying the providers for a session

Profiled AOT

The goal is to make it possible to add "something" to a webassembly project in order to cause it to collect a stack trace

• [mono][eventpipe] Implementing MethodDetails and BulkType events #68571
• Add a hook to start an EventPipe Session from runtime startup

Sample profiling

The goal is to make it possible to collect a meaningful profile of the main browser thread while it is running managed code

• Figure out why no samples are collected for a mostly async app.
• Identify a good default sampling frequency

Streaming EventPipe sessions

The goal is to make it possible to create a WebSocket connection back to the dev server to send live streaming EventPipe session data to the user.

Diagnostic server support

The goal is to make it possible to start and stop EventPipe sessions using a dotnet-dsrouter and dotnet-counters/dotnet-trace/etc combo when running a dev server.

Author:	lambdageek
Assignees:	-
Labels:	arch-wasm, untriaged, area-Tracing-mono
Milestone:	-