feat: handle DoS node by sending block

[yiweichi]

Problem

Malicious peers can DoS the node by sending old blocks.

Solution

Two-layer defense:

1. Finalized Block Protection
   if block_number <= finalized_height { penalize(peer); // Immediately reject}
2. Duplicate Block Detection
   // Cache recent blocks per peerif peer_already_sent_this_block { penalize(peer); // DoS detected }

Fixes #307

[codspeed-hq]

Merging this PR will not alter performance

✅ 2 untouched benchmarks

---

_{Comparing feat-penalize-peer-on-duplicate-block (624e663) with main (b77ae04)}

[frisitano]

Looks good. Added a few comments inline. Can you add some test cases, please?

I'm also wondering if we can simplify the logic a bit. The idea would be that if we have a connection with a peer over scroll-wire, then we should only gossip on scroll-wire. If we don't have a scroll-wire connection, then we use eth-wire. I think this should allow us to consolidate the block cache per peer into a single cache.

[frisitano]

Addeed some comments inline.

[yiweichi]

I'm planing to build a v1.0.7-rc0 image and deploy it on sepolia reth-rpc-0, then keep an eyes on the connected peer of it, do you think that make sense? @frisitano