fix: zetaclient should pick up new connector and erc20 custody addresses

[ws4charlie]

Description

1. Zetaclient should be able to refresh connector/erc20Custody addresses at runtime.
2. Added unit tests.

Closes: 1633

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.

• Tested CCTX in localnet
• Tested in development environment
• Go unit tests
• Go integration tests
• Tested via GitHub Actions

Checklist:

• I have added unit tests that prove my fix feature works

[codecov]

Codecov Report

Attention: Patch coverage is 77.21519% with 18 lines in your changes are missing coverage. Please review.

Project coverage is 48.14%. Comparing base (f2fde15) to head (70e541e).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1890      +/-   ##
===========================================
- Coverage    48.55%   48.14%   -0.42%     
===========================================
  Files          232      233       +1     
  Lines        13098    13317     +219     
===========================================
+ Hits          6360     6411      +51     
- Misses        6296     6464     +168     
  Partials       442      442              

Files	Coverage Δ
zetaclient/bitcoin/bitcoin_client.go	13.30% <ø> (+0.01%)	⬆️
zetaclient/evm/evm_client.go	14.85% <ø> (ø)
zetaclient/evm/evm_signer.go	47.93% <92.10%> (+2.09%)	⬆️
zetaclient/bitcoin/bitcoin_signer.go	0.00% <0.00%> (ø)
zetaclient/zetacore_observer.go	18.09% <74.28%> (ø)

[lumtis]

@ws4charlie now the client and signer for each chain update dynamically the chain params?

Can we confirm the following?

• If new chain support is setup but no activated yet isSupported=false, the ZetaClient will actively start supporting the chain when isSupported is changed to true in the chain param and we don't need to restart ZetaClient
• If we want to remove support for a chain, we can simply set isSupported to false in the chain param and ZetaClient will automatically stop interacting with the chain without the need to be restarted

[ws4charlie]

@ws4charlie now the client and signer for each chain update dynamically the chain params?

Can we confirm the following?

• If new chain support is setup but no activated yet isSupported=false, the ZetaClient will actively start supporting the chain when isSupported is changed to true in the chain param and we don't need to restart ZetaClient
• If we want to remove support for a chain, we can simply set isSupported to false in the chain param and ZetaClient will automatically stop interacting with the chain without the need to be restarted

1. Dynamically pause/unpause a connected chain is tracked by this issue: zetaclient should check 'IsSupported' flag to be able to pause/unpause a specific chain #1883
2. Dynamically add a new chain is a manual process which will at least involve
   • Observers runners update their zetaclient config files and zetaclient should be able to take new config file dynamically.
   • Zetaclient should be able to detect newly added chain with IsSupported flag enabled.
   • Zetaclient should also be able to dynamically create new ChainClient and ChainSigner objects and start new threads.

[lumtis]

Dynamically add a new chain is a manual process which will at least involve
Observers runners update their zetaclient config files and zetaclient should be able to take new config file dynamically.
Zetaclient should be able to detect newly added chain with IsSupported flag enabled.
Zetaclient should also be able to dynamically create new ChainClient and ChainSigner objects and start new threads.

We should implement all of this. Let's track issues if those don't exist

[ws4charlie]

Dynamically add a new chain is a manual process which will at least involve
Observers runners update their zetaclient config files and zetaclient should be able to take new config file dynamically.
Zetaclient should be able to detect newly added chain with IsSupported flag enabled.
Zetaclient should also be able to dynamically create new ChainClient and ChainSigner objects and start new threads.

We should implement all of this. Let's track issues if those don't exist

#1904

[lumtis]

Looks good.

One comment, and need to address build failure

[kevinssgh]

Looks good