Refactor: Gateway functions to get Gateway address dynamically

[fadeev]

Update both functions in packages/client/src and tasks in packages/tasks/src for:

• evm call
• evm deposit
• evm deposit and call
• zetachain call
• zetachain withdraw
• zetachain withdraw and call

Remove gatewayEVM/gatewayZEVM from the argument list. Instead, import the JSON from protocol contract's npm and find gateway address. I don't think we can use getAddress, because the functions in the client/src don't have access to chain labels specified in hardhat config, so the idea is for a function to get chain ID from the signer and find the gateway address based on chain ID.

Make txOptions optional.

Extract common functionality like parsing value array in a separate file to be reused across functions.

Make these functions convenient to use both from Hardhat tasks as well as the frontend, because the next task is to update the UniversalKit with these functions.

[fadeev]

It's also important to keep in mind that these functions are also used in localnet, which has a gateway address that changes, so it should be possible to pass the gateway address manually.

[fadeev]

@lukema95 for context, I think the way it works right now is a bit ugly:

    const tx = await client.evmDepositAndCall({
      amount: args.amount,
      erc20: args.erc20,
      gatewayEvm: args.gatewayEvm,
      receiver: args.receiver,
      revertOptions: {
        callOnRevert: args.callOnRevert,
        onRevertGasLimit: args.onRevertGasLimit,
        revertAddress: args.revertAddress,
        revertMessage: args.revertMessage,
      },
      txOptions: {
        gasLimit: args.gasLimit,
        gasPrice: args.gasPrice,
      },
      types: ["address", "bytes", "bool"],
      values: [args.target, args.recipient, JSON.stringify(args.withdraw)],
    });

https://github.com/zeta-chain/example-contracts/blob/08d15c55ffba27dc64bd17aca2a7fe88f6b5e061/examples/swap/tasks/swapFromEVM.ts

I want to get rid of the gateway param, for testnet and mainnet this value is read from protocol contracts, but for localnet that's not the case.

I see two options:

1. Being able to customize contract addresses from new ZetaChainClient({})
2. Or keep gateway as param, but make it optional

When localnet starts, it creates a file localnet.json:

{
  "pid": 97125,
  "addresses": [
    {
      "chain": "zetachain",
      "type": "gatewayZEVM",
      "address": "0x5FC8d32690cc91D4c39d9d3abcBD16989F875707"
    },
    {
      "chain": "zetachain",
      "type": "systemContract",
      "address": "0xCf7Ed3AccA5a467e9e704C703E8D87F634fB0Fc9"
    },

Maybe we do something like this:

    const jsonData = JSON.parse(fs.readFileSync("localnet.json", "utf8")); // if hre.network.name === localhost
    const contracts = jsonData?.addresses;
    const client = new ZetaChainClient({ signer, contracts });

If contracts are provided to ZetaChainClient, use those, otherwise, the client should fetch the correct addresses from protocol contracts.

[lukema95]

@lukema95 for context, I think the way it works right now is a bit ugly:

    const tx = await client.evmDepositAndCall({
      amount: args.amount,
      erc20: args.erc20,
      gatewayEvm: args.gatewayEvm,
      receiver: args.receiver,
      revertOptions: {
        callOnRevert: args.callOnRevert,
        onRevertGasLimit: args.onRevertGasLimit,
        revertAddress: args.revertAddress,
        revertMessage: args.revertMessage,
      },
      txOptions: {
        gasLimit: args.gasLimit,
        gasPrice: args.gasPrice,
      },
      types: ["address", "bytes", "bool"],
      values: [args.target, args.recipient, JSON.stringify(args.withdraw)],
    });

https://github.com/zeta-chain/example-contracts/blob/08d15c55ffba27dc64bd17aca2a7fe88f6b5e061/examples/swap/tasks/swapFromEVM.ts

I want to get rid of the gateway param, for testnet and mainnet this value is read from protocol contracts, but for localnet that's not the case.

I see two options:

1. Being able to customize contract addresses from new ZetaChainClient({})
2. Or keep gateway as param, but make it optional

When localnet starts, it creates a file localnet.json:

{
  "pid": 97125,
  "addresses": [
    {
      "chain": "zetachain",
      "type": "gatewayZEVM",
      "address": "0x5FC8d32690cc91D4c39d9d3abcBD16989F875707"
    },
    {
      "chain": "zetachain",
      "type": "systemContract",
      "address": "0xCf7Ed3AccA5a467e9e704C703E8D87F634fB0Fc9"
    },

Maybe we do something like this:

    const jsonData = JSON.parse(fs.readFileSync("localnet.json", "utf8")); // if hre.network.name === localhost
    const contracts = jsonData?.addresses;
    const client = new ZetaChainClient({ signer, contracts });

If contracts are provided to ZetaChainClient, use those, otherwise, the client should fetch the correct addresses from protocol contracts.

For functions, we can make the gatewayEvm parameter optional. When the gatewayEvm parameter is missing, we can obtain the corresponding contract address through the network and chain fields of ZetachainClient. What do you think?

[fadeev]

@lukema95 Eventually, I want to have contracts in the zetachain client constructor, but for now yes, let's start with what you suggested.