use batch tx validation in eth validator

[mattsse]

we currently create a new state provider per tx:

reth/crates/transaction-pool/src/validate/eth.rs

Lines 348 to 352 in fb64997

	let account = match self
	.client
	.latest()
	.and_then(|state| state.basic_account(transaction.sender()))
	{

this could be optimized if we validate txs in batches and only open the latest state once.

this needs some changes so that we can cache the provider when iterating over a list of txs

cc @hai-rise

          btw @hai-rise a similar problem exists here:

reth/crates/transaction-pool/src/validate/eth.rs

Lines 66 to 83 in fb64997

	pub fn validate_one(
	&self,
	origin: TransactionOrigin,
	transaction: Tx,
	) -> TransactionValidationOutcome<Tx> {
	self.inner.validate_one(origin, transaction)
	}
	/// Validates all given transactions.
	///
	/// Returns all outcomes for the given transactions in the same order.
	///
	/// See also [`Self::validate_one`]
	pub fn validate_all(
	&self,
	transactions: Vec<(TransactionOrigin, Tx)>,
	) -> Vec<TransactionValidationOutcome<Tx>> {
	transactions.into_iter().map(|(origin, tx)| self.validate_one(origin, tx)).collect()

this could use the same provider for all txs, could easily do this if we flip these

Originally posted by @mattsse in #13382 (comment)

[Elvis339]

Hey! This seems interesting, can I take this?

[PedroRosalba]

May I take this issue on?