eth: make tracers respect pre-EIP158/161 rules

[holiman]

This PR is on top of #18502 .
The tracers, when computing the statedb in various places, told the statedb.Finalise method to delete empty objects, and did not check whether EIP 158/161 was activated.
This causes erroneous traces for historic transactions, as seen in #18331

EDIT: rebased now that #18502 is merged

[holiman]

pingng @mtbitcoin -- for Etherscan, you might need to re-execute those same old transactions with this PR (a few of them are reported in the linked tickets) because Etherscan shows the erroneous traces.

Also, it might make sense for Etherscan to use the functionality from #17914 to provide more complete traces with less resource-intensive processing.

[mtbitcoin]

@holiman can you provide a sample txhash with the "erroneous traces" ?

[holiman]

From the original bug report, here's one:
https://etherscan.io/tx/0xfb200dc759b00dc69c0578fbce9df31d08c97dc33bc82c84c3b92f3071a4f65b
Gas used (correct): 37888
Trace: https://etherscan.io/vmtrace?txhash=0xfb200dc759b00dc69c0578fbce9df31d08c97dc33bc82c84c3b92f3071a4f65b at step 270 it says the gascost is 25061, which is incorrect.

[holiman]

Fixes #18331 , #17590 and #16693