Add block number to mempool_executed logs

[m-lord-renkse]

Description

Add block number to mempool_executed logs, so we can simulate failed submissions in order to debug the reason of the failure.

[squadgazzz]

so we can simulate failed submissions in order to debug the reason of the failure

Which data is expected to be used in order to simulate it(apart from the block number)? An example of the reverted txs: https://aws-es.cow.fi/_dashboards/goto/6d4fcd16a939814d07fbec7d5e72660e?security_tenant=global
It contains 2 txs inside with a huge amount of access lists.

[m-lord-renkse]

so we can simulate failed submissions in order to debug the reason of the failure

Which data is expected to be used in order to simulate it(apart from the block number)? An example of the reverted txs: https://aws-es.cow.fi/_dashboards/goto/6d4fcd16a939814d07fbec7d5e72660e?security_tenant=global It contains 2 txs inside with a huge amount of access lists.

The access list is not really needed for the simulation, it saves gas, but it can be simulated without it.

[sunce86]

nit: can be also (as data types are clear):

#[error("Mined reverted transaction: {0:?}, block: {1:?}")]
Revert(eth::TxId, eth::BlockNo),

[m-lord-renkse]

@sunce86 we show this as a debug version of it. I would keep it as in the logs will say tx_id and block_number, IMO better than seeing only a hashed and a number without saying what it is.

[sunce86]

I thought it's gonna be BlockNo(123456789)