Update logs + do not downscore peers if WE time out (#1901)

## Issue Addressed

- RPC Errors were being logged twice: first in the peer manager and then again in the router, so leave just the peer manager's one 
- The "reduce peer count" warn message gets thrown to the user for every missed chunk, so instead print it when the request times out and also do not include there info that is not relevant to the user
- The processor didn't have the service tag so add it
- Impl `KV` for status message
- Do not downscore peers if we are the ones that timed out

Other small improvements

beacon_node/eth2_libp2p/src/behaviour/mod.rs

@@ -1,5 +1,5 @@
 use crate::behaviour::gossipsub_scoring_parameters::PeerScoreSettings;
-use crate::peer_manager::{score::PeerAction, PeerManager, PeerManagerEvent};
+use crate::peer_manager::{score::PeerAction, ConnectionDirection, PeerManager, PeerManagerEvent};
 use crate::rpc::*;
 use crate::service::METADATA_FILENAME;
 use crate::types::{GossipEncoding, GossipKind, GossipTopic, MessageData, SubnetDiscovery};
@@ -70,8 +70,6 @@ pub enum BehaviourEvent<TSpec: EthSpec> {
         id: RequestId,
         /// The peer to which this request was sent.
         peer_id: PeerId,
-        /// The error that occurred.
-        error: RPCError,
     },
     RequestReceived {
         /// The peer that sent the request.
@@ -692,14 +690,24 @@ impl<TSpec: EthSpec> Behaviour<TSpec> {
                         // Inform the peer manager of the error.
                         // An inbound error here means we sent an error to the peer, or the stream
                         // timed out.
-                        self.peer_manager.handle_rpc_error(&peer_id, proto, &error);
+                        self.peer_manager.handle_rpc_error(
+                            &peer_id,
+                            proto,
+                            &error,
+                            ConnectionDirection::Incoming,
+                        );
                     }
                     HandlerErr::Outbound { id, proto, error } => {
                         // Inform the peer manager that a request we sent to the peer failed
-                        self.peer_manager.handle_rpc_error(&peer_id, proto, &error);
+                        self.peer_manager.handle_rpc_error(
+                            &peer_id,
+                            proto,
+                            &error,
+                            ConnectionDirection::Outgoing,
+                        );
                         // inform failures of requests comming outside the behaviour
                         if !matches!(id, RequestId::Behaviour) {
-                            self.add_event(BehaviourEvent::RPCFailed { peer_id, id, error });
+                            self.add_event(BehaviourEvent::RPCFailed { peer_id, id });
                         }
                     }
                 }