feat(prune): Add MerkleChangeSets segment

[RomanHodulak]

Closes #18463

Adds a pruner for change sets.

Change sets are newly persisted in the database and need to be pruned along with the rest of the entities to preserve space on full nodes.

[mediocregopher]

One missing functionality that should be easy to fix, plus naming suggestion.

Question: when pruning runs, does it also update the pipeline sync checkpoint which is stored? Or how should the engine check what range of data is actually available to be used?

[RomanHodulak]

Answer: The pipeline will run the pruner, then check its output and save it's checkpoint.

reth/crates/prune/prune/src/pruner.rs

Lines 214 to 221 in 1b9f9e2

	let segment_output = segment.prune(
	provider,
	PruneInput { previous_checkpoint, to_block, limiter: limiter.clone() },
	)?;
	if let Some(checkpoint) = segment_output.checkpoint {
	segment
	.save_checkpoint(provider, checkpoint.as_prune_checkpoint(prune_mode))?;
	}

[mediocregopher]

Answer: The pipeline will run the pruner, then check its output and save it's checkpoint.

reth/crates/prune/prune/src/pruner.rs

Lines 214 to 221 in 1b9f9e2

	let segment_output = segment.prune(
	provider,
	PruneInput { previous_checkpoint, to_block, limiter: limiter.clone() },
	)?;
	if let Some(checkpoint) = segment_output.checkpoint {
	segment
	.save_checkpoint(provider, checkpoint.as_prune_checkpoint(prune_mode))?;
	}

Hmm, I think this is the pruning checkpoint though, which is different than the pipeline sync checkpoint. So probably I'll need to update how the bounds check is working for engine API...

[mediocregopher]

LGTM 👍