EALREADY when reconnecting socket after destroying immediately after connecting

### Version v22.10.0 ### Platform ```text Darwin xxx.local 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:21 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T8103 arm64 ``` ### Subsystem _No response_ ### What steps will reproduce the bug? ``` import { Socket } from 'node:net'; const socket = new Socket(); socket.on('error', (err) => { console.log(err); }); socket.on('connect', () => { console.log('connected'); }); socket.connect({ host: 'google.com', port: 80 }); socket.once('close', () => { console.log('closed'); socket.connect({ host: 'google.com', port: 80 }); }); socket.destroy(); ``` ### How often does it reproduce? Is there a required condition? Always ### What is the expected behavior? Why is that the expected behavior? Seeing ``` closed connected ``` in the console. ### What do you see instead? ``` closed Error: connect EALREADY 142.250.179.174:2404 - Local (192.168.178.178:61323) at internalConnect (node:net:1097:16) at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18) at GetAddrInfoReqWrap.emitLookup [as callback] (node:net:1496:9) at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:132:8) { errno: -37, code: 'EALREADY', syscall: 'connect', address: '142.250.179.174', port: 2404 } ``` ### Additional information Calling `socket.destroySoon();` or `socket.end();` does work as intended, but IMO `socket.destroy();` should also allow a reconnect immediately afterwards. Note that calling `socket.destroy();` on a socket that has been connected does allow for immediate reconnect afterwards as expected.