feat(kona-exex): Init Derivation Pipeline

[refcell]

Description

Note

Based on paradigmxyz/reth-exex-examples#12

Issue #4 sets up the first part of the kona-exex, waiting on the L2 origin block.

This ticket is to initialize the derivation pipeline without setting up the main loop.

    /// Starts the Kona Execution Extension loop.
    pub async fn start(mut self) -> Result<()> {
		// Step 1: Wait for the L2 origin block to be available

		// Step 2: Initialize the Derivation Pipeline

		todo!("run the main loop")
    }

Reference: https://github.com/paradigmxyz/reth-exex-examples/pull/12/files#diff-fb2ecd571a8b660d914eac307e6aed9fc4fa610ad0b5521145d0fd6115e963dbR260-R292

Since the KonaExEx holds the providers to commit updates, initializing the derivation pipeline within KonaExEx is the most straightforward place.

use kona_derive::online::EthereumDataSource;
use super::types::{LocalPipeline, LocalAttributesBuilder, new_local_pipeline};

impl KonaExEx {
	...

    /// Initializes the derivation pipeline with the L2 origin block.
    pub async fn init_pipeline(&mut self, origin_l1_block: BlockInfo) -> LocalPipeline {
        let dap = EthereumDataSource::new(
            self.chain_provider.clone(),
            self.blob_provider.clone(),
            &self.cfg,
        );
        let attributes = LocalAttributesBuilder::new(
            self.cfg.clone(),
            self.l2_provider.clone(),
            self.chain_provider.clone(),
        );
        new_local_pipeline(
            self.cfg.clone(),
            self.chain_provider.clone(),
            self.l2_provider.clone(),
            dap,
            attributes,
            origin_l1_block,
        )
    }

	...
}