Remove is_valid_block_hash change in Deneb

[ppopth]

Since is_valid_block_hash is used in consensus-specs only for describing what verify_and_notify_new_payload does, is_valid_block_hash does not really exist in the clients.

is_valid_block_hash shouldn't accept parent_beacon_block_root, since it has nothing to do with them.

verify_and_notify_new_payload accepts parent_beacon_block_root and corresponds to engine_newPayloadV3, but is_valid_block_hash doesn't have to do the same.

[mkalinin]

is_valid_block_hash shouldn't accept parent_beacon_block_root, since it has nothing to do with them.

parentBeaconBlockRoot is a part of EL block but not a part of ExecutionPayload, CL must pass it to block hash verification, otherwise, EL won't be able to compute the actual block hash and do the validation

[ppopth]

parentBeaconBlockRoot is a part of EL block but not a part of ExecutionPayload, CL must pass it to block hash verification, otherwise, EL won't be able to compute the actual block hash and do the validation

Alright, got it. Thanks.