fix(consensus): record commit-sync fetch faults on the serving peer

[VorobyevIlya]

Description of change

The fast and regular commit syncers dropped peer-attributable fetch faults that the transaction-sync path already records, so honest validators could end up with different per-peer misbehavior counts depending on which path served the data.

• Malformed or unrequested transaction entries and payloads failing verification against their refs are now charged to the serving peer as unprovable faults on both commit-sync paths, matching the transaction-sync path.
• Fetched headers are now verified against the requested set instead of by position: an unrequested, duplicate, or malformed header is charged to the serving peer, as is a response with more entries than requested (new TooManyFetchedHeadersReturned, rejected before parsing).
• Incomplete responses stay untracked (FetchedTransactionsMismatch, NotEnoughHeadersFetched, renamed from UnexpectedNumberOfHeadersFetched): the server may lack the data or clip the request to its own local limits, and the client keeps partial data on mid-stream errors, so an honest response can arrive incomplete. Truncation only drops whole entries, which is why faults inside a delivered entry remain attributable.

Links to any relevant issues

fixes #12362

How the change has been tested

• Basic tests (linting, compilation, formatting, unit/integration tests)
• Patch-specific tests (correctness, functionality coverage)
• I have added tests that prove my fix is effective or that my feature works
• I have checked that new and existing unit tests pass locally with my changes