Add timestamp to simulate logs & blob gas & remove total difficulty

[deffrian]

Fixes Closes Resolves #

eth_simulateV1/ethSimulate-simple-send-from-contract (nethermind)
eth_simulateV1/ethSimulate-override-address-twice-in-separate-BlockStateCalls (nethermind)
eth_simulateV1/ethSimulate-eth-send-should-produce-logs (nethermind)
eth_simulateV1/ethSimulate-eth-send-should-produce-more-logs-on-forward (nethermind)
eth_simulateV1/ethSimulate-empty-with-block-num-set-firstblock (nethermind)
eth_getBlockByNumber/get-genesis (nethermind)
eth_getBlockByHash/get-block-by-hash (nethermind)
eth_getBlockByNumber/get-block-london-fork (nethermind)

There is a bug in geth that sets timstamps to zero in eth simulate
For context: ethereum/go-ethereum#32831

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Description

Testing

[LukaszRozmej]

I say leave it for AuRa and Clique
If we really want we can remove (by setting null) in past blocks if we are post-merge. But that probably will still fail the test.

But the test is shit as TD is valid property for pre-merge blocks and Geth just yolo removed it.

[deffrian]

I would remove it as well. Rn now we store it in the db for no apparent reason
Do we use clique anywhere? I think at this point we can remove it with ethash. And we probably should

[LukaszRozmej]

1. Japan Open Chain still uses Clique and is supported.
2. We still have some Clique and AuRa uses, but they are not officially supported networks.
3. We still need AuRa and Ethash for full syncing networks that were merged later (mainnet, gnosis). We could probably rip out large part from them, but can't remove them completely. But it is an effort.

Thus lets not do sudden moves without proper plan and scope.