De-obfuscate stack traces for errors offline

In https://github.com/flutter/devtools/pull/8385, we are de-obfuscating stack traces in process. That means that we are reporting the Dart file and location names of the stack when DevTools encounters an error. However, if you were to try to open a link to any of those locations, it would fail. This is because although we are bundling the source map with the release, we are not including the actual Dart sources.

Another option (as described by @sigmundch) is to still show the obfuscated stack traces in any reported error, but add automation to de-obfuscate them within our tools, e.g. I believe the Dart VM is using a Github action that can be called to de-obfuscate a stack trace reported in a bug.

Note: I'm opening this up to keep track of what is needed if we decide that the changes in https://github.com/flutter/devtools/pull/8385 aren't sufficient for our use case.

审查 PR 8385 及其对已去混淆堆栈跟踪、source maps 和打包 Dart 源代码的处理方式。将该方法与 Dart VM 工具中用于对报告的跟踪进行去混淆的拟议自动化方案进行比较。完成标准是记录或实现一个可行的离线工作流，以支持打开报告的源代码位置。

由索引模型根据 Issue 内容生成。