Improve categorization of smart-contracts' methods

[nikitosing]

Close #4557

Changelog

Bug fixes:

• Fix impossibility to query read methods of proxy smart contracts (not its implementation)

Enhancements

• Improve things was done in Hide error selector in the contract's functions list #4612
• Duplicate methods stateMutability=nonpayable methods with at least one output the Read Contract page
• Add wallet connection section to Read Contract page if there are stateMutability=nonpayable methods with at least one output
• Add field from to the eth_call for aforementioned methods

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

[vbaranov]

@nikitosing I suppose, differentiating read-only methods with modifiers as methods that have no input parameters and have output parameters is wrong. At least, because, read-only method with modifiers can accept input parameters as well. In that case, it is hard or impossible to differentiate the read-only method with modifier and wite method. Let's discuss this internally.