Use --no-minify-wasm when creating devtools for releases.

[biggs0125]

In order to better debug WASM-specific errors, disable minification of wasm builds of devtools.

Also adds support for the flag to the local development CLI so that it can be used when debugging wasm locally.

The --no-minify-wasm flag was added here:
flutter/flutter@85486ff

[biggs0125]

@kenzieschmoll Does this have to wait to land until after the pinned Flutter candidate has been updated to include the change I linked to above?

[kenzieschmoll]

@kenzieschmoll Does this have to wait to land until after the pinned Flutter candidate has been updated to include the change I linked to above?

Yes, otherwise the flag will likely be a no-op or the build will fail if passing the flag prior to your flutter change would cause a crash.

[biggs0125]

@kenzieschmoll Does this have to wait to land until after the pinned Flutter candidate has been updated to include the change I linked to above?

Yes, otherwise the flag will likely be a no-op or the build will fail if passing the flag prior to your flutter change would cause a crash.

The flag would be unrecognized without that other change so I think it would likely crash. I'll hold off landing this until that version bump happens.

[kenzieschmoll]

You can go ahead and update the Flutter hash in this PR. Update the hash in flutter-candidate.txt to a0711824a5bac6a4bb9703b5e11601004db3d14b (the latest in g3 which looks like it does include your change)