Revisit prune_modes argument for the BatchExecutor

[shekhirin]

Describe the feature

This API is weird because prune_modes feels out of place in it

reth/crates/evm/src/execute.rs

Lines 173 to 175 in 3bf3b9e

	/// The pruning modes are used to determine which parts of the state should be kept during
	/// execution.
	fn batch_executor<DB>(&self, db: DB, prune_modes: PruneModes) -> Self::BatchExecutor<DB>

Additional context

No response

[mattsse]

this is only needed for the execution stage and imo it would be more appropriate if this is applied on the batch output and not handled by the executor.

the tmp mem overhead for full node sync is negligible imo

[shekhirin]

What if we just have a separate method that sets the prune modes? Like this one

reth/crates/evm/src/execute.rs

Lines 83 to 86 in 5fb81af

	/// Set the expected tip of the batch.
	///
	/// This can be used to optimize state pruning during execution.
	fn set_tip(&mut self, tip: BlockNumber);