Change order of proxy contracts patterns detection: existing popular EIPs to the top of the list

[vbaranov]

#8758

Motivation

Well-known standards (like EIP-1167, EIP-1967, EIP-1822) should have more priority before others.

Changelog

Put next piorities for proxy contracts detection:

1. EIP-1167 (internal research shows, most of the proxy-contracts follows this pattern)
2. EIP-1967
3. EIP-1822
4. All others

we also not only adding priorities but testing pattern match sequentionally for first 3 standards (if pattern matches, we do not run logic for the next pattern - this should lead to reducing the number of requests to the node).

Fix for EIP-1967 beacon proxy pattern detection.

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