Inconsistency among different clients on when to use a specific diconnect reason

As an example to this, when Geth disconnects a peer with a different network id with diconnection reason `0x10` (Other), whereas Nethermind disconnects a peer with a different network id with disconnection reason `0x03` (Useless Peer).

Because of this we are not able to know if the reason is NetworkId,or forkId for example. I think we need to relock at the disconnection reasons and work on a list that covers all cases.

if changing or adding to these messages is not an option or adding to then maybe we can come up with way for clients to send a details message explaining the reason for disconnection