build: wasip1 is broken on wasmedge runtime

[johanbrandhorst]

This is a tracking issue for issues surrounding the use of the new wasip1 GOOS target on the wasmedge Wasm runtime. We currently do not have a wasmedge runner.

This issue should not be considered done until we have a working wasmedge runner and all tests are either passing or we have documented the failures which we cannot reasonably fix.

Currently known failing tests:

Package	Test name	Error	Test log	Fixed
archive/zip	TestOpenReaderInsecurePath	Unable to write out the bugos zip entry	Full log	✔️
all	N/A	Test timeout	Full log

[gopherbot]

Change https://go.dev/cl/493696 mentions this issue: all: add wasmedge wasip1 runner

[gopherbot]

Change https://go.dev/cl/494120 mentions this issue: misc/wasm: add wasmedge to wasip1 script

[johanbrandhorst]

The runner has been created and once the builders have been redeployed I will run it to see where it fails.

[gopherbot]

Change https://go.dev/cl/495078 mentions this issue: misc/wasm: test commit

[gopherbot]

Change https://go.dev/cl/496076 mentions this issue: env: add runtime library to wasmedge runner

[johanbrandhorst]

OK after some fixes I managed to run the test suite against wasmedge and the first failure we're seeing is:

--- FAIL: TestOpenReaderInsecurePath (0.01s)
    reader_test.go:1386: Unable to write out the bugos zip entry
FAIL
FAIL	archive/zip	8.807s

I've updated the table at the top. This is a new type of error so more investigation will be necessary.

[gopherbot]

Change https://go.dev/cl/498616 mentions this issue: misc/wasm: set PATH variable in exec

[johanbrandhorst]

Seems this test failure fixed itself, but now we have a new failure:

##### Testing packages.
*** Test killed with quit: ran too long (4m0s).
signal: quit (core dumped)
FAIL	archive/tar	240.085s
*** Test killed with quit: ran too long (4m0s).
signal: quit (core dumped)
FAIL	archive/zip	240.090s
*** Test killed with quit: ran too long (4m0s).
signal: quit (core dumped)
FAIL	bufio	240.058s
FAIL
go tool dist: Failed: exit status 1

Looks like execution is a bit too slow at this time. I will experiment with increasing the timeout to see if run into any other errors.