Support multiple polytone evm connections on ica client

[Buckram123]

This PR aims to add support for multiple polytone connections on ica-client.

Implementation inspired by ibc-client

[Buckram123]

Up for discussion: It seems more common to use chain id as number instead of chain-name for evm chains, do we want to replace TruncatedChainId parts to

#[non_exhaustive]
enum IcaChainId {
  Cosmos(TruncatedChainId),
  Evm(u64),
}

@Kayanski @adairrr ?

[Kayanski]

Up for discussion: It seems more common to use chain id as number instead of chain-name for evm chains, do we want to replace TruncatedChainId parts to

#[non_exhaustive]
enum IcaChainId {
  Cosmos(TruncatedChainId),
  Evm(u64),
}

@Kayanski @adairrr ?

That's a good idea, Are we using this ICA Client for other purposes than EVM chains though ? Is it necessary to have Cosmos chains in there too ? We do have the IBC Client for that I think already ?
Otherwise, that's a very nice idea to have the ICA client work like the IBC client !

[Buckram123]

Up for discussion: It seems more common to use chain id as number instead of chain-name for evm chains, do we want to replace TruncatedChainId parts to

#[non_exhaustive]
enum IcaChainId {
  Cosmos(TruncatedChainId),
  Evm(u64),
}

@Kayanski @adairrr ?

That's a good idea, Are we using this ICA Client for other purposes than EVM chains though ? Is it necessary to have Cosmos chains in there too ? We do have the IBC Client for that I think already ? Otherwise, that's a very nice idea to have the ICA client work like the IBC client !

You are right, we're only using it for evm chains right now. It could be good to keep it as a multi-chain client as it has more functionality beyond helping evm executions and it is quite different from ibc client: each account controls it's own proxy on remote chain