feat: bitcoin dynamic depositor fee

[ws4charlie]

Description

1. Use Bitcoin block average fee rate in depositor fee calculation for Athens3 and mainnet
2. The tentative upgrade height for the dynamic fee is set at 832000 for mainnet. (in 14 days)

Closes: 1698

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?

• Go unit tests

The calculated fee rate of 9998/10000 mainnet blocks matched mempool.space, 2/10000 of blocks saw a diff of 1 sat/vB.

result_mainnet.txt
result_testnet.txt

[github-actions]

!!!WARNING!!!
nosec detected in the following files: zetaclient/bitcoin/bitcoin_client.go, zetaclient/bitcoin/inbound_tracker.go, 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.

[lumtis]

Regarding zetaclient/testdata/bitcoin_block_828440.json
Do we need the entire data for the block?
I think we should trim to only keep what we need.

[ws4charlie]

Regarding zetaclient/testdata/bitcoin_block_828440.json Do we need the entire data for the block? I think we should trim to only keep what we need.

Good idea. I can set the tx input/output as nil to make the block compact.

[ws4charlie]

Regarding zetaclient/testdata/bitcoin_block_828440.json Do we need the entire data for the block? I think we should trim to only keep what we need.

trimmed in commit