Build `dart2wasm`-compiled DevTools with `--minify` flag

[elliette]

Currently we ship the unminified version of DevTools when compiled with dart2wasm:

devtools/tool/build_release.sh

Line 85 in 22c619f

--no-minify-wasm

This is because:

1. with the --no-minify-wasm flag, we get detailed exception messages in our analytics
2. since all of the DevTools assets are served from the developer's local machine, the code size shouldn't affect IPL time too much

However, we would like to switch to using the minified version after the initial stable release with dart2wasm as default (Dart 3.11 / Flutter 3.41)

@mkustermann @osa1 are currently working on adding to decode production errors with the minified dart2wasm build, so as part of switching to the minified version we should also configure DevTools to use this tooling.

[kenzieschmoll]

@elliette is this ready to implement? Do you have a pointer to the tooling to decode production errors, and did you have a plan in mind for where we should be using this decoder?

[elliette]

[@elliette](https://github.com/elliette) is this ready to implement? Do you have a pointer to the tooling to decode production errors, and did you have a plan in mind for where we should be using this decoder?

I haven't looked into this since filing this issue - @mkustermann @osa1 what is the status on the tooling to decode production errors? Thanks!