cmd/dist: enable all js/wasm tests that should pass in dist

[bradfitz]

@neelance, please modify cmd/dist/test.go to enable all tests you expect to pass for js/wasm.

I disabled a bunch of tests in 7d50abf because I needed to finally see some black on the dashboard for the js-wasm column to be able to enable trybots and start catching regressions (like #26014)

/cc @cherrymui

[neelance]

I didn't know that you were waiting on this. I'm not currently running the tests this way on my machine. Looking into it now. I need to make sure that env GOOS=js GOARCH=wasm ./bin/go tool dist test passes, right?

[bradfitz]

Test:

$ GOOS=js GOARCH=wasm ./all.bash

... which ultimately calls dist. But yes, you can test it with go tool dist test too.

Note parts of https://github.com/golang/go/wiki/PortingPolicy mentioning all.bash:

Once those conditions are satisfied, the Go team can accept the port and begin to merge the CLs. Once the CLs are all submitted, all.bash must pass, so that the builder reports "ok" in the dashboard.

Any port started during a release cycle must be finished (all.bash passing, builder reporting "ok") before the corresponding release freeze, or else the code will be removed at the freeze.

[gopherbot]

Change https://golang.org/cl/120796 mentions this issue: cmd/dist: enable more tests on js/wasm

[neelance]

@bradfitz Thanks!