feat(rpc): add configurable EVM memory limit

[wojtek0x]

Describe the feature

Currently, the only constraint on how much memory the EVM can allocate indirectly comes from the gas cap.
If the gas cap is set very high, it’s possible for a program to request more memory than the host system can provide. This can lead to Reth crashing with an error such as:

memory allocation of 30957566848569344 bytes failed

To prevent such out-of-memory crashes, Reth could support an explicit EVM memory limit configuration.

Proposed Solution
Introduce a command-line flag to cap the maximum memory the EVM can allocate per RPC request:

--rpc.evm-memory-limit <MB>

Additional context

We run Reth with --rpc.gas-cap set to uint64::MAX to support complex EVM computations.
Occasionally Reth crashes due to buggy contracts that attempt invalid allocations (e.g., MSTORE with a huge offset). We haven't run into this problem with Geth, which appears to have additional memory limit check and returns MemoryOOG in such situation.

[wojtek0x]

If the request sounds reasonable, I'm happy to contribute with a PR. I believe the feature is straightforward, I've put together a PR on the revm side: https://github.com/bluealloy/revm/pull/3109/files. I'm curious what the Reth team thinks about this.

[mattsse]

I think this is reasonable

iirc you're running with unlimited gas?

we should add some sane limits here to avoid this, @rakita wdyt a sane limit for eth_call would be?

@wojtek0x

the fix should happen here

reth/crates/rpc/rpc-eth-api/src/helpers/call.rs

Lines 793 to 795 in 96218b3

	// Disable block gas limit check to allow executing transactions with higher gas limit (call
	// gas limit): https://github.com/paradigmxyz/reth/issues/18577
	evm_env.cfg_env.disable_block_gas_limit = true;

for cfg_env.memory_limit

but I'm not sure why this is currently bypassed