Fix intermitent condition where onerror is called when conn is closed by client

[ngbrown]

The test "onerror is not called when conn is closed by client" intermittently fails.

According to some resources, such as RFC-1122 (4.2.2.12 Closing a Connection): if the host actively closes a connection, while still having unread incoming data available, the host should send the signal RST (losing any received data) instead of FIN. This may or may not be what is happening, but there's there's something causing a RST to be received by the client at least some of the time.

This pull request proposes the solution of calling socket.destroy() in closeSocket() to ignore the possibility of a RST response. This was also the solution in postwait/node-amqp#444.

See recent past failures:

• https://github.com/cloudamqp/amqp-client.js/actions/runs/5131090828/job/13886861954#step:14:98
• https://github.com/ngbrown-forks/amqp-client.js/actions/runs/5613121714/job/15208428472#step:14:99
• https://github.com/ngbrown-forks/amqp-client.js/actions/runs/5601476456/job/15174015021#step:14:70

[dentarg]

Nice, this gets rid of the amqp-client connection closed read ECONNRESET seen when running the README example #64 (comment)

[dentarg]

There should be an option to allow maintainers to push to your branches/PRs, then I can update (rebase) and merge them, so you don't have to do all that work, and will look like they was merged too. :)

[ngbrown]

There should be an option to allow maintainers to push to your branches/PRs, then I can update (rebase) and merge them, so you don't have to do all that work, and will look like they was merged too. :)

I've seen that option on Pull Requests in GitHub in the past, but it's not there on these PRs. It might be because I'm forking into an separate account/org?

[dentarg]

I've seen that option on Pull Requests in GitHub in the past, but it's not there on these PRs.

I saw it working for another PR, it said (in the right side-bar) Maintainers are allowed to edit this pull request.

It might be because I'm forking into an separate account/org?

Sounds like that reading https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork

Who can use this feature

People with push access to the upstream repository of a fork owned 
by a personal account can commit to the forked branches.