fix Bun.connect(localhost) overly preferring ipv6

[nektro]

makes more progress towards passing the https://github.com/sidorares/node-mysql2 test suite

one of the diffs is from changing a test that was added in a fix for https://github.com/oven-sh/bun/issues/7355. below is proof the actual issue has not regressed.

[github-actions[bot]]

❌ @nektro 13 files with test failures on bun-darwin-aarch64:

• test/cli/inspect/inspect.test.ts 16 failing
• test/cli/install/registry/bun-install-registry.test.ts 131 failing
• test/cli/test/bun-test.test.ts 1 failing
• test/integration/next/default-pages-dir/test/dev-server.test.ts 1 failing
• test/js/bun/http/serve.test.ts 1 failing
• test/js/bun/net/socket.test.ts 5 failing
• test/js/bun/net/tcp-server.test.ts 5 failing
• test/js/node/net/node-net.test.ts 3 failing
• test/js/node/watch/fs.watchFile.test.ts 1 failing
• test/js/third_party/webpack/webpack.test.ts 1 failing
• test/js/web/fetch/fetch.test.ts SIGTERM
• test/js/web/websocket/websocket-upgrade.test.ts 1 failing
• test/regression/issue/06443.test.ts 2 failing

View test output

^{#453196bdf844e1adb9f086bb0f6201bf47dc578d}

[github-actions[bot]]

❌ @nektro 14 files with test failures on bun-darwin-x64:

• test/cli/inspect/inspect.test.ts 16 failing
• test/cli/install/registry/bun-install-registry.test.ts 131 failing
• test/cli/test/bun-test.test.ts 1 failing
• test/integration/next/default-pages-dir/test/dev-server.test.ts 2 failing
• test/js/bun/http/serve.test.ts 1 failing
• test/js/bun/net/socket.test.ts 5 failing
• test/js/bun/net/tcp-server.test.ts 5 failing
• test/js/bun/util/which.test.ts 1 failing
• test/js/node/fs/fs.test.ts 1 failing
• test/js/node/net/node-net.test.ts 3 failing
• test/js/third_party/webpack/webpack.test.ts 1 failing
• test/js/web/fetch/fetch.test.ts SIGTERM
• test/js/web/websocket/websocket-upgrade.test.ts 1 failing
• test/regression/issue/06443.test.ts 2 failing

View test output

^{#453196bdf844e1adb9f086bb0f6201bf47dc578d}

[github-actions[bot]]

❌ @nektro 12 files with test failures on linux-x64-baseline:

• test/cli/inspect/inspect.test.ts 16 failing
• test/cli/install/registry/bun-install-registry.test.ts 131 failing
• test/cli/test/bun-test.test.ts 1 failing
• test/integration/next/default-pages-dir/test/next-build.test.ts 1 failing
• test/js/bun/http/serve.test.ts 1 failing
• test/js/bun/net/socket.test.ts 5 failing
• test/js/bun/net/tcp-server.test.ts 5 failing
• test/js/node/net/node-net.test.ts 3 failing
• test/js/third_party/webpack/webpack.test.ts 1 failing
• test/js/web/fetch/fetch.test.ts SIGTERM
• test/js/web/websocket/websocket-upgrade.test.ts 1 failing
• test/regression/issue/06443.test.ts 2 failing

View test output

^{#453196bdf844e1adb9f086bb0f6201bf47dc578d}

[github-actions[bot]]

❌ @nektro 13 files with test failures on linux-x64:

• test/cli/inspect/inspect.test.ts 16 failing
• test/cli/install/registry/bun-install-registry.test.ts 131 failing
• test/cli/test/bun-test.test.ts 1 failing
• test/integration/esbuild/esbuild.test.ts 1 failing
• test/integration/next/default-pages-dir/test/next-build.test.ts 1 failing
• test/js/bun/http/serve.test.ts 1 failing
• test/js/bun/net/socket.test.ts 5 failing
• test/js/bun/net/tcp-server.test.ts 5 failing
• test/js/node/net/node-net.test.ts 3 failing
• test/js/third_party/webpack/webpack.test.ts 1 failing
• test/js/web/fetch/fetch.test.ts SIGTERM
• test/js/web/websocket/websocket-upgrade.test.ts 1 failing
• test/regression/issue/06443.test.ts 2 failing

View test output

^{#453196bdf844e1adb9f086bb0f6201bf47dc578d}

[7f8ddd]

I believe this was (and may still be) an issue that makes the debugger not work. It'll say the port is in use when it's not. There's an issue somewhere about it already. I personally just gave up on trying, as the workaround involved editing the hosts file to remove the :: entries.