feat(rpc-client): Introduce rpc-jsonrpsee Crate

[refcell]

Description

Introduces an op-alloy-rpc-jsonrpsee crate that can replace the non-type logic reth/optimism/rpc. Type logic can go in op-alloy/rpc-types.

Closes #32

[refcell]

Note

Depends on sync types from #35

[mattsse]

perhaps we rename this to op-alloy-jsonrpsee ?

[refcell]

Note

Adds the OutputResponse type to rpc-types since it's used by the trait. Takes care of #32

[HrikB]

I wanna ask if it makes sense to implement a Provider here over the Optimism network. I was doing smth like this:

#[async_trait]
pub trait OpStackProvider<T: Transport + Clone = BoxTransport>: Provider<T, Optimism> {
    async fn output_at_block(&self, block_number: u64) -> TransportResult<OutputAtBlock> {
        let response = self
            .client()
            .request("optimism_outputAtBlock", (format!("0x{:x}", block_number),))
            .await?;

        Ok(response)
    }
}

impl<T: Transport + Clone> OpStackProvider<T> for RootProvider<T, Optimism> {
}

[mattsse]

yep this makes sense, mind opening an issue for this?
this should go into a new provider crate