stCreate2::create2collisionStorage

[enitrat]

• create2collisionStorage_d0g0v0_Shanghai: fails because the account has no code nor nonce and a storage that is not empty initially. The expected behavior is that the storage is cleared - however, we do not clear the storage on purpose, as This can only happen in the following highly unlikely circumstances:

  • The address created by a CREATE call collides with a subsequent CREATE or CREATE2 call.
  • The first CREATE happened before Spurious Dragon and left empty code - which cannot happen in our case

• create2collisionStorage_d1g0v0_Shanghai: same issue, previous storage not cleared

• create2collisionStorage_d2g0v0_Shanghai: same

[ClementWalter]

should we do something here then? or is it just like that and we don't care (but add a doc somewhere with know failing cases)