feat: initiated feature of zetaclient-restricted-address

[ws4charlie]

Description

1. Added ComplianceConfig field to config file where observers can fill in a blacklist of evm addresses and bitcoin addresses (can be mixed)
2. Any inbound transaction (ZetaSent, ERC20Deposit, Gas deposit) that involves a banned address (Sender or Receiver or txOrigin) will be ignored by observers.
3. Any registered outbound cctx will be cancelled if it involves a banned address (Sender or Receiver). The cctx cancellation is done by zeroing out the amount of Zeta/ERC20/Gas token sent to Receiver.

Closes: 1789

Zeta and ERC20 Deposited

Restricted EVM address and BTC address

Gas token to TSS. Banned EVM address and BTC address

Outbound banned address is tested in e2e tests PR #1791

Example log file:
compliance.log

Example zetaclient config:

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

[github-actions]

!!!WARNING!!!
nosec detected in the following files: zetaclient/bitcoin/utils.go

Be very careful about using #nosec in code. It can be a quick way to suppress security warnings and move forward with development, it should be employed with caution. Suppressing warnings with #nosec can hide potentially serious vulnerabilities. Only use #nosec when you're absolutely certain that the security issue is either a false positive or has been mitigated in another way.

Only suppress a single rule (or a specific set of rules) within a section of code, while continuing to scan for other problems. To do this, you can list the rule(s) to be suppressed within the #nosec annotation, e.g: /* #nosec G401 */ or //#nosec G201 G202 G203
Broad #nosec annotations should be avoided, as they can hide other vulnerabilities. The CI will block you from merging this PR until you remove #nosec annotations that do not target specific rules.

Pay extra attention to the way #nosec is being used in the files listed above.

[codecov]

Codecov Report

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

Project coverage is 8.23%. Comparing base (ea1da8b) to head (e948d7d).

Additional details and impacted files

@@            Coverage Diff             @@
##           develop   #1790      +/-   ##
==========================================
+ Coverage     8.10%   8.23%   +0.12%     
==========================================
  Files          251     252       +1     
  Lines        62166   62279     +113     
==========================================
+ Hits          5041    5126      +85     
- Misses       56743   56765      +22     
- Partials       382     388       +6     

Files	Coverage Δ
x/crosschain/keeper/evm_deposit.go	55.93% <100.00%> (-6.93%)	⬇️
zetaclient/bitcoin/inbound_tracker.go	0.00% <0.00%> (ø)
zetaclient/bitcoin/utils.go	74.16% <85.71%> (+4.55%)	⬆️
common/utils.go	6.45% <0.00%> (-3.55%)	⬇️
zetaclient/common/utils.go	18.18% <18.18%> (ø)
zetaclient/evm/inbounds.go	13.30% <30.76%> (+13.30%)	⬆️
zetaclient/evm/evm_signer.go	0.00% <0.00%> (ø)
zetaclient/bitcoin/bitcoin_signer.go	0.00% <0.00%> (ø)
zetaclient/evm/evm_client.go	0.30% <0.00%> (-0.01%)	⬇️
zetaclient/bitcoin/bitcoin_client.go	13.34% <27.14%> (+4.05%)	⬆️