Address gas_limit checking

[poplexity]

On the EVM contract there is currently no check to ensure we do not accept a transaction who's gas limit is > the block's gas limit. We need to do 2 things, possibly 3:

1. Add check to the EVM contract to prevent such transactions from being put into blocks
2. Check that we don't already have any such transactions on chain (testnet & mainnet) via kibana or another approach
3. If we find that we have larger transactions, we need to account for these by either a. Increasing global gas limit for blocks, so we can handle them b. Dynamically increase gas_limit in the block header if there is a trx which exceeds the limit. It looks like reth has a check that we don't increase to quickly (looks like previous_block.gas_limit / 1024 is the biggest increase allowed)

[poplexity]

Per @guilledk:

we have 4 transactions on mainnet acording to this rpc that go over the 0x7fffffff gas limit:

• 0x8a4f502aad5a6fbb50437b093c3b0fa58fdb526398311ebff18afcf584a248f6
• 0xd82f6d19c1d91acf3702c8e50355dc64cc09dce14957cbb67faca120e70ce9ff
• 0x1f660e429580b38c683fb08aba35930fe890fad98eb2824d2f4bd66c1caadb4b
• 0x7c8103359ffb78f73692c7e31d4c5079cb68644d936587483d10df338d49c9e2

[poplexity]

We have implemented a fix, allowing block gas_limit to go up beyond the limit mentioned above, so we now do this dynamically.

Created https://github.com/telosnetwork/telos.evm/issues/178 to add a check in the contract to protect against this going forward.