Add new libp2p subprotocol for msg-ack flow

[tolbrino]

Currently the entire msg + ack workflows are split into separate unidirectional subprotocols issues and handled as separate code paths. This causes several complications:

1. it is difficult to pair Ack for each Msg
2. in case of missing Ack the Msg protocol is still considered successful, but it should fail
3. there is no automatic pairing of Ack and Msg even for failed messages
4. workflows requiring bi-directional logic can not be easily used over the msg + ack combination and the implementation is overly complex.
5. introduce sampled message latency tracking over the new bi-directional protocol

It'd be beneficial to finally unite both subprotocols into a single one and implement relevant fixes to known subprotocol issues related to HOPR protocol.

Description

The new msg + ack protocol will have a single RequestId allowing it to be trackable together. That in turn allows to fix some of the major issues of the current design, including:

• Use the new msg/ack protocol to randomly sample the peer connection instead of the heartbeat protocol, when messages pass through it
• Always ack the msg request, even on msg failure, to increase the privacy
• Simplify the packet processing pipeline to abstract away from the non-transport related behavior (e.g. tickets, chain ops...)
• Update the code to use lazy initialization where possible and optimize background processes with true parallelization (e.g. rayon).
• Optimize the large data object pass-through in the pipelines to improve throughput
• Support the legacy protocol and allow the new protocol to be used/attempted to use by default.

Relevant issues

• Limit non-cooperative nodes who do not send ACKs #2649
• relates to Improve libp2p hopr subprotocol (v0.2.0) #5662
• Optimization of the packet processing pipeline #5891
• Create p2p abstraction layer between HOPR and libp2p #5894
• 🐛 Acknowledge *every* packet #5937
• Abstract packet processing DB operations to a standalone trait #6050
• Refactor select! block in SwarmEventLoop's run method for better readability #6262

Definition of DONE

• A new msg + ack protocol is defined in term of the RequestResponse libp2p behavior
• The new protocol is the default protocol
• The legacy protocol is supported in a backwards compatible manner
• Randomly selected latency measurements are taken from the new protocol
• The process pipeline is streamlined and simplified
• The new abstractions are in place to allow removing non-transport related code from the transport layer and hide those behind a trait
• Lazy initialization is used wherever possible
• Packet processing pipeline uses a parallelization engine