feat: includes peer_id as a label in the MessageSendBytesTotal and MessageReceiveBytesTotal Prometheus metrics

[staheri14]

Inline with #1077

Our past experimentation showed that none of the current Prometheus traffic related metrics encompass all the information regarding the message type, peer ID and channel ID. This deficiency can be addressed by incorporating peer IDs for message_receive_bytes_total and message_send_bytes_total. This PR provides this feature.

I tested it by executing a local validator node and examining the Prometheus metrics endpoint. Here's an example of the output:

cometbft_p2p_message_send_bytes_total{chID="0x40", chain_id="mocha-4", message_type="blockchain_StatusResponse", peer_id="cb7adca6fbaabc5336c5eebbc1312390a2bb9d2d", version="1.0.0-rc0-278-g4c452c5f4"} 8

[cmwaters]

Do you think the bandwidth may vary per peer?

[staheri14]

Do you think the bandwidth may vary per peer?

Good question, Indeed, it can and it does, especially in scenarios involving request-reply protocols (like in the CAT mempool), or when a connected peer is lagging behind and attempting to synchronize, as this often results in a substantial portion of network traffic being consumed by that peer.