test,win: enable tcp_connect_error_after_write

[bnoordhuis]

The test was added in 2012 but never enabled on Windows. Let's see how it fares anno 2023.

[cjihrig]

LGTM if it passes.

[bnoordhuis]

For posterity, the write fails with EPIPE instead of EBADF, which I guess is as valid an error as any other?

1: # Output from process `tcp_connect_error_after_write`:
1: # Assertion failed in D:\a\libuv\libuv\test\test-tcp-connect-error-after-write.c on line 68: `UV_EBADF == uv_write(&write_req, (uv_stream_t*) &conn, &buf, 1, write_cb)` (-4083 == -4047)

[vtjnash]

I might have made a rebase mistake?

2: not ok 314 - tcp_connect_error_after_write
2: # exit code -1073740791
2: # Output from process `tcp_connect_error_after_write`:
2: # Assertion failed in D:\a\libuv\libuv\test\test-tcp-connect-error-after-write.c on line 85: `r == 0` (-4047 == 0)

[bnoordhuis]

Huh, STATUS_STACK_BUFFER_OVERRUN? I'll take a look.

[bnoordhuis]

Still happens after a rebase, with changes only to the test file. -4047 is UV_EPIPE and that's a basically impossible return code from uv_run() so I guess that means the buffer overrun status code doesn't come out of completely thin air.

[vtjnash]

We used to have an ASAN test until it seemed that GithubActions updated something and broke it: #4210

[vtjnash]

seems that ASAN didn't have anything to report

not ok 314 - tcp_connect_error_after_write
# exit code -1073740791
# Output from process `tcp_connect_error_after_write`:
# Assertion failed in D:\a\libuv\libuv\test\test-tcp-connect-error-after-write.c on line 85: `r == 0` (-4047 == 0)