PeerReputation - timeouts are indexed by request code which does not take into account protocol

[macfarla]

Fix - either index by protocol as well as message code - or don't track timeouts per request type at all (simplify) - what is it giving us to track them separately?

ie eth message code 1 and snap message code 1 would both end up counted together

  public Map<Integer, AtomicInteger> timeoutCounts() {
    return timeoutCountByRequestType;
  }

log does not mention protocol but this is snap

2024-04-02 14:47:51.725+10:00 | EthScheduler-Timer-0 | DEBUG | PeerReputation | Disconnection triggered by 3 repeated timeouts for requestCode 1
2024-04-02 14:47:51.725+10:00 | EthScheduler-Timer-0 | DEBUG | EthPeers | Disconnected EthPeer 0xcfe6f6424d1f2255...

[pr9t]

Hey, I am interested in this issue. Please assign this to me.