Considering `SELFDESTRUCT`

As @xiaohanzhu suggested, it could be possible to `SELFDESTRUCT` a contract and deploy a different contract at the same address. How is this possible @xiaohanzhu ? If so, at the moment we don't handle this situation.

One workaround might be allowing retriggering a contract verification.

Also how do other block explorers handle this case?

_{View in Huly HI-357}

No files, tests, or entry points are named. Start by tracing how Sourcify handles verification when a contract is destroyed and redeployed at the same address, then review how other block explorers handle this case. Define the expected behavior and a verification test before implementing any change.

Written by the indexing model from the issue text.