EIP-7594: Specify data column sidecar verification functions to run

[nalepae]

For by root and by range requests checks, the exact function to run is specified for KZG commitments, but not for the inclusion proof.

This PR aligns both checks.

[nalepae]

Additional question: Should the SHOULD be replaced by a MUST?

Consequences could be quite dramatic if a client actually considers a block with data column sidecars with invalid inclusion proof and/or invalid KZG proofs as available.

[jtraglia]

Additional question: Should the SHOULD be replaced by a MUST?

Precedent says no. For example, the equivalent check for BlobSidecarsByRoot:

consensus-specs/specs/deneb/p2p-interface.md

Line 294 in 57483cb

Before consuming the next response chunk, the response reader SHOULD verify the blob sidecar is well-formatted, has valid inclusion proof, and is correct w.r.t. the expected KZG commitments through `verify_blob_kzg_proof`.

[jtraglia]

Thanks. I like explicitly calling out those functions.

Could we mention verify_data_column_sidecar too?

[ppopth]

LGTM. However, I agree with @jtraglia that we should mention verify_data_column_sidecar too.

[nalepae]

Thank you for the remark and change @jtraglia!