POC Support ZkEvm

[catalyst17]

Detecting ZK EVM contracts deployment is done similar to the OP stack way. In short:

• for all the contracts we check for the new contract deployed with the specific hash of a code_change
• 3 of those deployments are done through the ZkEVMDeployerContract, so for these we additionally check the NewDeterministicDeployment event emittance
• 2 contracts are deployed under a usual TransparentUpgradeableProxy so for these there is extra logic
  • for the main PolygonZkEvm under a proxy we are checking that there is a set of very specific events along the deployment
  • for the PolygonZkEVMGlobalExitRoot under the same proxy type we are even doing an RPC read call to the implementation address to make sure we detected the correct proxy address

Again, I think one of the next steps should probably be to start using Substreams store modules in order to make sure we are correctly enriching one rollup entity instead of creating a new one, because right now we're relying on the separate sink logic to merge the data when updating data in Postgres, which doesn't seem to work well (we miss a lot of contracts' addresses for OP).

Another improvement I figured at the very end of this PR's work is to use RPC read calls in substreams to actually query the majority of the periphery contracts' addresses from one of the main contracts which can hold [almost] all of them.

[linear]

BLOCK-1340 POC support zkEVM

[tomedalya]

Overall it looks pretty straight forward.
there are method ids and some other constants that would be better to have them either commented with names or with proper names as statics so will be easier to understand what are we searching .

pretty high level review so would be good to have second pair of eyes