sockets: Add error code for EPIPE (and ECONNABORTED on Windows)

[badeend]

WASI sockets currently has no error code corresponding to EPIPE. When writing to a closed/broken socket:

• POSIX systems return EPIPE
• Windows returns ECONNABORTED

After searching around, this Windows-specific discrepancy is well-known:

• Android ADB, Mio, and OpenJDK treat it as EPIPE.
• libuv and nginx treat it as ECONNRESET.

---

WASI doesn't have a good solution for it now:

• By the time the OS reports EPIPE, previously acknowledged writes may have been lost and and the guest should be informed about that. So swallowing the error is not right.
• Mapping it to ECONNRESET isn't right either, beause that implies that the peer actively reset the connection.
• Mapping (or: leaving) it as ECONNABORTED isn't optimal either, because that error code is usually only returned by accept and sometimes connect on Unix-like systems.

I think this warrants a new error code. I've called it connection-broken. I expect wasi-libc to map this to EPIPE.

---

Wasmtime currently maps EPIPE to ok(()). With the new error code in place, this test can be updated to consistently expect an error cross platform.

[alexcrichton]

Rationale and everything makes sense to me FWIW, seems reasonable to me!

[badeend]

@ricochet I'm not allowed to merge my own PRs. Would you mind merging this for me?

[ricochet]

Ah we need approval from someone else in WASI Sockets Champions. Overriding now