chore: expose PruneConfig in CLI args

[garwahl]

This PR closes #9816 and addresses #9808

This PR exposes PruneConfig via the CLI so that users can adjust any pruning configuration, similar to how it is adjusted in reth.toml currently.

cc @emhane

[emhane]

This PR attempts to close #9816

This draft currently has two outstanding questions.

• Same question as Expose entire prune config in CLI args #9816 (comment), how will --full interact with any of the individual PruneModes being set? Do we expect --prune.receipts.distance 64 to be able to be used with --full as an example.

I'd say, any more specific flags than --full, take precedence over --full. so --full currently sets default prune modes (as opposed to archive node which doesn't prune). setting --full --prune.receipts.distance <u64> would set all prune modes with defaults, except for receipts, which would be set to the the value passed to --prune.receipts.distance.

• For configuring ReceiptsLogFilter this looks like it takes an Address:PruneMode pair, how do we expect this to look like as a CLI arg, ie --prune.receiptslogfilter address:distance:64,address2:before:64,address3:full or something else?

lgtm

cc @emhane

[garwahl]

cc @emhane This is ready for review now PTAL

[emhane]

looking good!

[garwahl]

@emhane do you mind kicking off another run of the pipeline, lint should be fixed now. Thanks!

[garwahl]

@mattsse @Rjected @onbjerg @gakonst PTAL

[emhane]

remaining are lint fixes

[garwahl]

Hey @emhane could you kick off the lint again? I've run both ./book/cli/update.sh target/debug/reth and make pr after rebasing off main and not getting any diff

[garwahl]

@emhane do you mind running the lint on this PR and pushing to the branch, I've run ./book/cli/update.sh target/debug/reth and make pr after pulling in upstream main and not seeing any diffs. Perhaps my local configuration is broken

[emhane]

@emhane do you mind running the lint on this PR and pushing to the branch, I've run ./book/cli/update.sh target/debug/reth and make pr after pulling in upstream main and not seeing any diffs. Perhaps my local configuration is broken

I was struggling with the book too, removing this extension in VS code solved it for me. this extension was recommended by vs code, hence why I installed it in the first place.

[garwahl]

@emhane do you mind running the lint on this PR and pushing to the branch, I've run ./book/cli/update.sh target/debug/reth and make pr after pulling in upstream main and not seeing any diffs. Perhaps my local configuration is broken

I was struggling with the book too, removing this extension in VS code solved it for me. this extension was recommended by vs code, hence why I installed it in the first place.

🤔 I'm running RustRover as an IDE.

I'd be very surprised if the dev env impacts ./book/cli/update.sh which looks like it runs ./book/cli/help.py under the hood but 🤷

[garwahl]

Could you sanity check and rebuild the book from this branch and see if you get the diff? I can't see why the IDE would impact it