Stack traces are obfuscated

In https://github.com/Dart-Code/Dart-Code/pull/5367#issuecomment-2532490346 I noted the stack traces for some errors were not very useful because of minification/wasm. After discussing with @kenzieschmoll we believed this might be VS Code-specific so to try and compare I checked what I'm getting outside of DevTools.

I can't repro the same issue, however I can force the kind of error noted at https://github.com/Dart-Code/Dart-Code/issues/5158#issuecomment-2497856004 by just running:

```
dt serve --dtd-uri ws://localhost:1234/invalid
```

When using WASM, this is what I see:


It's not clear to me if this is expected or not. There are some `.dart` files and line numbers in the call stack, but there are also some `main.dart.wasm` with hex offsets and all of the function names are obfuscated.

If I do the same without WASM, the function names are all still obfuscated although the top of the stack has some extra filenames that weren't in the wasm version (for example `logger_helpers.dart:34`).


I'm not certain that this is wrong, but the screenshots from @elliette at https://github.com/Dart-Code/Dart-Code/issues/5158#issuecomment-2504607675 seem like they have much better information than here.

Comienza reproduciendo el error reportado con `dt serve --dtd-uri ws://localhost:1234/invalid` y compara los stack traces de WASM y no-WASM. Lee las issues y el pull request enlazados de Dart-Code para conocer la salida esperada; se considera terminado cuando se haya determinado si los nombres y offsets ofuscados son esperados y se haya identificado la discrepancia relevante en caso contrario.

Escrito por el modelo de indexación a partir del texto del issue.