Contract interaction: fix nested tuples in the output view, add formatting

[vbaranov]

Motivation

Nested tuple outputs cause 500 server error.

Changelog

• Process method call output recursively
• Add formatting of nested output types

Checklist for your Pull Request (PR)

• 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 by submitting a PR to https://github.com/blockscout/docs
• If I added/changed/removed ENV var, I submitted a PR to https://github.com/blockscout/docs to update the list of env vars at https://github.com/blockscout/docs/blob/master/for-developers/information-and-settings/env-variables.md and I updated the version to master in the Version column. Changes will be reflected in this table: https://docs.blockscout.com/for-developers/information-and-settings/env-variables.
• If I add new indices into DB, I checked, that they are not redundant with PGHero or other tools

[coveralls]

Pull Request Test Coverage Report for Build c32287293faf63bb32592328c02525a876887bc0-PR-3592

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 62 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+3.2%) to 65.429%

---

Files with Coverage Reduction	New Missed Lines	%
lib/block_scout_web/checksum_address.ex	6	55.56%
lib/block_scout_web/views/smart_contract_view.ex	56	36.67%

Totals
Change from base Build aff90fbd651751d4347cb74dc212f97a16af8bf4:	3.2%
Covered Lines:	2080
Relevant Lines:	3179

---

💛 - Coveralls