Spike for Allo v2 on ZKSync

[0xOneTony]

Here is how you deploy contracts on Allo
https://github.com/allo-protocol/allo-v2/tree/main/deploy

The key things which we found out was:

• A project can have same anchor address on EVM chains except era cause the anchor is derived from the Registry.sol address and it's not possible to deploy the contract with the same address on era and EVM chains
• We needed to use era libraries so we had to rewrite the deploy scripts. additional the remapping is a little differnt and we ended up having a custom remapping file for era (captured in the readme marked above)
• Allo.createPool relies on cloning the strategy address but in era you would need to know the strategy contract bytecode at compile time and not runtime. This means that we cannot use createPool and we end up using createPoolWithCustomStrategy. To still get the benefits of cloning, we ended up writing factory contract per strategy (which is annoying to scale) and that can be found at https://github.com/allo-protocol/allo-v2/tree/main/contracts/factories. The read me there are captures why these factory contracts exsist

When we look at account abstraction / other changes to the contract. It would be worth checking the compaibility for era and if it's not , have fallback functions to ensure allo is usable on era