Add polygon edge support

[sl1depengwyn]

Fix #7090

Motivation

It turned out that Polygon edge trace is very different from geth trace, so it does not work now

Changelog

Added separate tracer for geth to work with polygon.

There are some limitations:

• call ops are very strange in polygon edge, example:

{
                "pc": 3132,
                "op": "CALL",
                "gas": 492083345,
                "gasCost": 7400,
                "depth": 2,
                "stack": [],
                "memory": [],
                "storage": {}
}

so, to field in these cases is 0x0000000000000000000000000000000000000000

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 (Update env-variables.md for #7513 docs#158)
• 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