feat: add an instrument to portal-bridge for more clear logs

[KolbyML]

What was wrong?

I was trying to read through bridge logs and I couldn't tell if they were coming from the history or beacon bridge. This makes grepping and debugging hard.

How was it fixed?

with this change all the logs generated by the history bridge are marked by history and all the logs generated by the beacon bridge are tagged with beacon

2024-01-06T15:47:10.139336Z  INFO history: surf::middleware::logger::native: request completed    
2024-01-06T15:47:10.143257Z DEBUG history:send_async{method=POST uri=https://erigon-lighthouse.mainnet.eu1.ethpandaops.io/}:handler{id=8}: isahc::handler: Connection #0 to host erigon-lighthouse.mainnet.eu1.ethpandaops.io left intact
2024-01-06T15:47:10.290635Z DEBUG history: portal_bridge::bridge::history: Gossip: Block #18949112 Receipts
2024-01-06T15:47:10.321927Z DEBUG history: hyper::client::connect::http: connecting to 127.0.0.1:8545
2024-01-06T15:47:10.322390Z DEBUG history: hyper::client::connect::http: connecting to 127.0.0.1:8545
2024-01-06T15:47:10.322571Z DEBUG history: portal_bridge::gossip: Unable to locate content on network, after failing to gossip, retrying in 15s seconds. content key="0x028ae09f4a4939679fe55e0481dc24fc4a69ca9a87ba8c22dd8fe52b6597949352"

previously it was unclear for example which bridge generated DEBUG: portal_bridge::gossip, but now it is marked DEBUG history: portal_bridge::gossip

This also improves grepibility since you can just grep logs by network which is awesome.

[ogenev]

LGTM 👍

[njgheorghita]

🥳