feat(ARCO-295): new log level in p2p

[pawellewandowski98]

Description of Changes

Add option to provide different log level for peers. Added TRACE level for even more descriptive logs.

Example:

blocktx-2     | Dec  6 08:30:25.096 DBG-4 Received peer.network=TestNet peer.address=node2:18333 cmd=AUTHCH
blocktx-2     | Dec  6 08:30:25.096 DBG-4 Received peer.network=TestNet peer.address=node2:18333 cmd=SENDHEADERS
blocktx-2     | Dec  6 08:30:25.096 DBG-4 Received peer.network=TestNet peer.address=node2:18333 cmd=SENDCMPCT
blocktx-2     | Dec  6 08:30:25.096 DBG-4 Received peer.network=TestNet peer.address=node2:18333 cmd=PING
blocktx-2     | Dec  6 08:30:25.096 DBG-4 Sent peer.network=TestNet peer.address=node2:18333 instance=0 cmd=PONG

NOTE: Requires #686 to be merged first

Linked Issues / Tickets

ARCO-295

Testing Procedure

Describe the tests you've added or any testing steps you've taken.

• I have added new unit tests
• All tests pass locally
• I have tested manually in my local environment

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have updated CHANGELOG.md with my changes

[sonarqubecloud]

Quality Gate failed

Failed conditions
60.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud