Add Fulu boilerplate

[macladson]

Proposed Changes

Adds Fulu fork boilerplate.

Additional Info

This makes no attempt to unify Fulu with PeerDAS. This will need to be a separate PR.

[dapplion]

@macladson I've applied the fork_enabled pattern on the remaining places where it is possible in this commit a543765 please review and consider cherry-picking into this PR

To motivate my case against the match fork_name:

• Relying on the type system to direct our dev attention to certain places would make sense ONLY if we add a new variant to ForkName once the fork is fully spec'ed. Otherwise (like here, now) we just fill all those match cases assuming the fork is empty, losing the all benefits of this approach. Let's accept that we are unlikely to wait for a full spec before adding the boilerplate.

[macladson]

Thanks for the commit! I agree with your reasoning and I've cherry-picked it into the main branch.

I ended up reverting the web3signer.rs changes as it actually uses a local variant of ForkName not types::ForkName so to remove that boilerplate, we'd either need to write a mapping from types::ForkName => web3signer::ForkName or rewrite the web3signer to use types::ForkName. I can't comment on why types::ForkName was chosen in the first place, but either way, it feels out of scope for this PR.

[dapplion]

Looks great! Send it

[jimmygchen]

Nice work @macladson and thanks for the review @dapplion! I've added a few more comments, let me know what you think. I think we can merge this soon 🎉

[jimmygchen]

Looks great, thanks @macladson!

[michaelsproul]

@mergify queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

Details

Pull request #6695 has been dequeued by a dequeue command.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

[michaelsproul]

@mergify dequeue

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #6695 has been dequeued by a dequeue command

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

[mergify]

dequeue

✅ The pull request has been removed from the queue default

[michaelsproul]

@mergify requeue

[mergify]

requeue

✅ This pull request will be re-embarked automatically

Details

The followup queue command will be automatically executed to re-embark the pull request

[mergify]

queue

🛑 The pull request has been removed from the queue default

Details

Pull request #6695 has been dequeued by a dequeue command.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

[michaelsproul]

@mergify dequeue

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #6695 has been dequeued by a dequeue command

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

[mergify]

dequeue

✅ The pull request has been removed from the queue default

[michaelsproul]

@macladson this needs some updates for the clippy lints https://github.com/sigp/lighthouse/actions/runs/12702656555/job/35409240281?pr=6785

[michaelsproul]

@mergify queue

[mergify]

queue

✅ The pull request has been merged automatically

Details

The pull request has been merged automatically at ecdf2d8