feat: create header proof using BeaconBlockElectra

[morph-dev]

This is a followup of #1799

What was wrong?

We are missing logic for creating header proof using BeaconBlockElectra.

How was it fixed?

Added function for creating proof.
Note that we don't have any test vectors to verify if this works as intended.

To-Do

• Clean up commit history and use conventional commits.

[morph-dev]

This logic is triggered after processing era file. Do you think this will be needed?
Also, at the moment, we decide which fork to use based on block number, and we don't have one for Pectra yet.

[KolbyML]

We have the timestamp it will be enabled already

[KolbyML]

https://github.com/alloy-rs/hardforks/blob/535da0c7b265084d6757f3f3e0dfd752b9d775a6/crates/hardforks/src/ethereum/mainnet.rs#L78

[morph-dev]

We would call it from here:

trin/bin/e2hs-writer/src/reader.rs

Lines 244 to 267 in afa57c1

	pub fn iter_blocks(mut self) -> impl Iterator<Item = anyhow::Result<AllBlockData>> {
	(self.starting_block..self.ending_block).map(move |current_block| {
	if current_block
	< EthereumHardfork::Paris
	.activation_block(network_spec().network().into())
	.expect("Paris should be available")
	{
	self.get_pre_merge_block_data(current_block)
	} else if current_block
	< EthereumHardfork::Shanghai
	.activation_block(network_spec().network().into())
	.expect("Shanghai should be available")
	{
	self.get_merge_to_capella_block_data(current_block)
	} else if current_block
	< EthereumHardfork::Cancun
	.activation_block(network_spec().network().into())
	.expect("Cancun should be available")
	{
	self.get_capella_to_deneb_block_data(current_block)
	} else {
	self.get_deneb_block_data(current_block)
	}
	})

and we only have block number available.
I'm not sure if/how we would refactor it...

[KolbyML]

There are post merge and pre-merge blocks, all post merge blocks use ERA, I don't think this current loop makes much sense tbh

[KolbyML]

We could do a match case on what CL fork the BeaconBlock is for, instead of blindly parsing it like we are now using block number

[morph-dev]

I refactored how it works.
I no longer check what fork we are on based on number, but rather based on variant of SignedBeaconBlock.
If you think it would be good, I can also add a check to make sure that variant is at the expected fork.

[KolbyML]

Yeah the changes look good.

If you think it would be good, I can also add a check to make sure that variant is at the expected fork.
I think this would be overkill to be honest, but either way it isn't like we are using hardcoded values anymore which is nice

[morph-dev]

@KolbyML, ready for a review.

[KolbyML]

looks good