Improve transaction validation flow

[trinhdn97]

The transaction validation flow now can be described as a separated two-step process.

1. The low cost basic validation step:

• The transaction types must be accepted in txpool and executable
• Value must not be negative
• IntrinsicGas ≤ GasLimit ≤ MaxGasLimit of chain
• GasFeeCap ≥ GasTipCap and they must not be extremely large numbers
• GasTipCap ≥ EffectiveMinTip of chain
• The sender is ecrecover-able from the transaction signature

2. The heavy state-related validation step:

• Nonce of from address must be greater or equal to current nonce
• Balance of from address must be enough to cover all the transaction cost of that address

Currently all transaction must pass both validation steps to be included in local txpool. While some processes in txpool require basic validation only, and some future process focus on state-related validations, such as paymaster/AA flow or future subpools. This leads to the need of breaking down the whole validation process first

[khoau2u]

Would removing the heavy step make certain denial-of-service attack vectors easier to exploit?