Add dev ChainOrchestrator / Service

[mattsse]

Describe the feature

for #7131 we need dev version of

reth/crates/node/builder/src/launch/engine.rs

Lines 208 to 223 in 98b214f

	// Configure the consensus engine
	let mut eth_service = EngineService::new(
	ctx.consensus(),
	ctx.components().block_executor().clone(),
	ctx.chain_spec(),
	network_client.clone(),
	Box::pin(consensus_engine_stream),
	pipeline,
	Box::new(ctx.task_executor().clone()),
	ctx.provider_factory().clone(),
	ctx.blockchain_db().clone(),
	pruner,
	ctx.components().payload_builder().clone(),
	TreeConfig::default(),
	ctx.invalid_block_hook()?,
	);

the thing that drives the chain forward, for dev mode, this is similar to the

reth/crates/consensus/auto-seal/src/task.rs

Line 24 in 98b214f

pub struct MiningTask<Client, Pool: TransactionPool, Executor, Engine: EngineTypes> {

but acts similar to:

reth/crates/engine/tree/src/tree/mod.rs

Line 402 in 98b214f

pub struct EngineApiTreeHandler<P, E, T: EngineTypes> {

or rather the persistence stuff

like a task that polls a local payload builder based on some mining mode and appends a new block

All of this should go into a new crate under engine, this should reuse the payload builder stack and not roll custom block building like the auto-seal-consensus does

Additional context

No response

[greged93]

@mattsse can I take this?