feat: use creation init on self destruct

[zachdaniel]

Resolves #1949 and #1950

Changelog

Enhancements

• Use the init of the creating internal transaction in the case that data is <<>> due to a self destruct. Display it on the code page, and disable contract verification for those contracts.

Bug Fixes

• Use Data.to_string/1 when rendering a raw trace of a create transaction.

  • I added an entry to CHANGELOG.md with this PR
  • If I added new functionality, I added tests covering it.
  • If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.
  • I checked whether I should update the docs and did so if necessary

[coveralls]

Pull Request Test Coverage Report for Build 1449cb44-eff0-4edb-806f-5419b32bed8d

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.04%) to 81.102%

---

Files with Coverage Reduction	New Missed Lines	%
apps/explorer/lib/explorer/chain/transaction_count_cache.ex	2	84.21%

Totals
Change from base Build 0b01fb7e-c0dc-4c70-ad07-e5014c0c8ca2:	-0.04%
Covered Lines:	4708
Relevant Lines:	5805

---

💛 - Coveralls

[ayrat555]

you're only checking contracts_creation_internal_transaction. should we also check contracts_creation_transaction if an address is created in the main transaction?

[zachdaniel]

This case is only possible if the contract was self destructed in the transaction that created it (self destructs in its constructor), so the main transaction in this case will always be the constructing transaction, and the create will always be an internal transaction. I'm pretty sure this is the case.