apollo_network: pass the reBadPeerReport when reporting

[guy-starkware]

Note

Medium Risk
Touches cross-crate networking interfaces and call sites; behavior should be equivalent but signature changes and new report construction could break integrations or misclassify peers if wired incorrectly.

Overview
Updates the broadcast peer-reporting API so BroadcastTopicClientTrait::report_peer now requires a BadPeerReport (peer id, BadPeerReason, and PenaltyCard) alongside the original BroadcastedMessageMetadata.

Consensus and mempool P2P are updated to construct and pass structured reports for specific cases (e.g., vote/tx conversion failures and duplicate votes), tests/mocks are adjusted accordingly, and the network crate docs/tests are updated; the current BroadcastTopicClient::report_peer still only forwards the metadata while logging the report (TODO to send it).

^{Written by Cursor Bugbot for commit a921ad3. This will update automatically on new commits. Configure here.}

[reviewable-StarkWare]

This change is 

[guy-starkware]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• apollo_network: pass the reBadPeerReport when reporting #12474 👈 (View in Graphite)
• apollo_network: struct that holds the reason the peer is considered bad #12470
• apollo_network: add BadPeerReport and PenaltyCard #12463
• apollo_consensus: check for duplicate votes before caching #12465
• apollo_consensus: add helper function to report peer #12464
• main-v0.14.1-committer

This stack of pull requests is managed by Graphite. Learn more about stacking.