PeerPool removePeer should allow code or reason as parameter - Closes #4083

[jondubois]

What was the problem?

The logs did not show the disconnect reason most of the time.

How did I solve it?

If the status reason is not provided by the other side of the socket, then use the default reason for that code from SocketCluster if it exists.

How to manually test it?

Run tests and check against testnet.

Review checklist

• The PR resolves PeerPool removePeer should allow code or reason as parameter #4083
• All new code is covered with unit tests
• Relevant integration / functional tests are added
• Commit messages follow the commit guidelines
• Documentation has been added/updated

[mitsuaki-u]

Code looks good but we should also do the following: 1. removePeer function in PeerPool should be modified to include reason 2. reason should be added to the removePeer calls in evictPeer and removeAllPeers

[jondubois]

@mitsujutsu Ready to review.