Contract interaction: array input type parsing fix

[vbaranov]

Resolves #3255

Motivation

Array input in contract interactions doesn't encode correctly

Changelog

Parse input types in order to check if array type presents and format input in that case

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

[github-actions]

Pull Request Test Coverage Report for Build bf93acf817b2ebeb2784a93a2295e1df0259283c-PR-3259

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-15.4%) to 55.155%

---

Totals
Change from base Build ea694bfffdd0948f2e06b72265039f00d7806fad:	-15.4%
Covered Lines:	444
Relevant Lines:	805

---

💛 - Coveralls