fix: close MultiaddrConnection once

[twoeths]

Title

Close MultiaddrConnection once

Description

• It's designed to close MultiaddrConnection once, however in case there are some writable data remaining, socket is not destroyed yet https://github.com/libp2p/js-libp2p/blob/c5003d40207bc3be15645b5af93f8dec1fd5d55b/packages/transport-tcp/src/socket-to-conn.ts#L177 and when there is a called to close() again it'll run the function again
• Instead use a variable to control it like other places

Notes & open questions

this could fix #2477 see https://github.com/libp2p/js-libp2p/issues/2477#issuecomment-2049121628

Change checklist

• [x] I have performed a self-review of my own code
• [x] No need documentation as the change is straightforward and small, the same pattern is applied in a lot of places
• [x] I thought about unit tests however not sure how to do it. This change is quite straightforward and scanned through the current tests through

[twoeths]

@achingbrain thanks for the suggestions, now I improved the test and it failed on main. I did a small modification on the maConn.abort() function not to destroy the socket if it's already destroyed to make sure the socket.destroy() is called once

this is all about maConn.close() being called multiple times and we want it to close once, this happens when socket.writableLength > 0 which is reflected in the test