Match block and blobs after validating execution

[dapplion]

Issue Addressed

After PeerDAS we request block and data to different peers. Consider the following scenario when doing a by range sync:

• Block at slot N contains no data
• Peer serving the block at slot N forges the block adding KZG commitments
• The peers serving data columns do not return any data columns for slot N

Current unstable will attempt to match block and columns and consider the entire RpcBlock invalid. A similar scenario can occur where the block peer is honest and the column peer is dishonest.

We need to make the code more aware of who is at fault, and specifically do not attempt to match columns before validating the block.

Part of

• Improve range sync with PeerDAS #6258

Note: this PR touches code on the mainnet path, not only PeerDAS

Proposed Changes

Relax RpcBlock construction with new_unchecked and perform matching in verify_kzg_for_rpc_block after the block is execution validated.

This PR does not include a fix for peer scoring. This will be tackled latter as part of #6258