Authenticated call support

[fadeev]

• gateway on three chains: Ethereum, BNB, ZetaChain (still on the same anvil instance)
• authenticated and arbitrary calls through callOptions
• automatically swap for gas tokens when handling reverts
• separate handling of depositedAndCalled and withdrawnAndCalled events
• onCall instead of onCrossChainCall
• sender info is in context.sender
• throw an error when function doesn't exist when making an arbitrary call

This version is being used in all E2E tests in zeta-chain/example-contracts#218

[fadeev]

Having both --is-arbitrary-call and --function "hello(string)" seems redundant: if a function is defined, then it's an arbitrary call. This was my criticism of the Gateway API. I'll be keeping it in the CLI interface so that it's still possible for users to test the scenario where isArbitraryCall is true, but there is no function defined.

[fbac]

@fadeev since localnet is getting more complex, could you include a brief explanation, or even better a diagram on how it is supposed to work? That would help greatly with the review process.

I'm thinking something similar to this diagram, where we can clearly see the entrypoints, what actor does what exactly, when is every handleXXX function called, etc.

[fadeev]

@fbac

https://www.figma.com/board/uABT4inqEYuRjgFY142xI2/Localnet?node-id=0-1&node-type=canvas

[fadeev]

@fbac @skosito please, review.

[lumtis]

utACK