fix(coverage): ensure contract hash to record coverage for is not zero

[grandizzy]

Motivation

• for contracts that are not already created the hash in interpreter is 0x. This leads to recording coverage for 0x hash instead of contract hash (and if multiple contracts created in same test then only the first one will have constructor covered).

Solution

• in coverage collector, if hash is 0 then recalculate it from contract bytecode

[klkvr]

hmm, wondering if this should be fixed in revm instead? cc @rakita

[grandizzy]

hmm, wondering if this should be fixed in revm instead? cc @rakita

yeah, I guess we could set init_code_hash to bytecode.hash_slow if it's 0 here: https://github.com/bluealloy/revm/blob/main/crates/revm/src/context/evm_context.rs#L295 but not sure about other side effects @rakita any insights highly appreciated! thank you!

[DaniPopes]

oops sorry didnt see the comments, in any case a fix here is fine for now

[grandizzy]

oops sorry didnt see the comments, in any case a fix here is fine for now

yep, will follow up if fix in revm too. Thanks!