feat: move core rpc server types to standalone crate

[leruaa]

ref #8460

[mattsse]

great start

with a standalone, lightweight crate we can also pull this in in reth-rpc and move the constants to reth-rpc-server-types

[mattsse]

solid,

next we need the remaining types that are used in node-core

[leruaa]

@mattsse Can you please have a look at my last commit and tell me if I'm heading in the right direction? Feels like I'm moving the entire rpc-builder crate...

[mattsse]

I see, the main problem is this config trait:

reth/crates/node-core/src/cli/config.rs

Line 18 in e75edf3

pub trait RethRpcConfig {

hmm, this is a bit tricky, I need to think about this a bit,

okay, for this pr, let's only do constants first, get the pr over the line and then continue with more incremental changes. it's fine if node-core then also depends on server-types.
but it will be easier to move stuff around once we have the crate

[leruaa]

@mattsse I think this is ready to be reviewed.

P.S.: Don't hesitate if you can think of some good first issues for the next steps :)

[mattsse]

lgtm

next we can move these constants and types for cache

reth/crates/node-core/src/args/rpc_state_cache.rs

Lines 2 to 5 in 13fcb88

	use reth_rpc::eth::cache::{
	DEFAULT_BLOCK_CACHE_MAX_LEN, DEFAULT_CONCURRENT_DB_REQUESTS, DEFAULT_ENV_CACHE_MAX_LEN,
	DEFAULT_RECEIPT_CACHE_MAX_LEN,
	};

then I think we move the config traits