Fix PeerDAS sync scoring

[dapplion]

Issue Addressed

Range sync will not penalize the proper peer during PeerDAS sync for invalid column errors

Proposed Changes

• Propagate errors with enough details to figure out which block component(s) are invalid
• Track which peer served what in range sync batches
• Use the above two ^ to downscore the correct peers

Progress

• Implement
• Add tests

[mergify]

Some required checks have failed. Could you please take a look @dapplion? 🙏

[mergify]

Some required checks have failed. Could you please take a look @dapplion? 🙏

[dapplion]

Last remaining CI failure is a clippy warning

error: large size difference between variants
  --> consensus/state_processing/src/per_epoch_processing/epoch_processing_summary.rs:12:1
   |
12 | /   pub enum EpochProcessingSummary<E: EthSpec> {

[dapplion]

• I have added store tests from Fix for #7305: Verify blobs and data columns during backfill #7353

[mergify]

Some required checks have failed. Could you please take a look @dapplion? 🙏

[mergify]

Some required checks have failed. Could you please take a look @dapplion? 🙏

[pawanjay176]

Looks good. Can start testing and fix the peer attribution in the other big sync PR

[mergify]

Some required checks have failed. Could you please take a look @dapplion? 🙏

[mergify]

Some required checks have failed. Could you please take a look @dapplion? 🙏

[mergify]

Some required checks have failed. Could you please take a look @dapplion? 🙏

[mergify]

All required checks have passed and there are no merge conflicts. This pull request may now be ready for another review.

[pawanjay176]

@jimmygchen Merge at will

[jimmygchen]

LGTM! Thanks for pushing this through 👍