feat: Bitcoin utxo consolidation

[ws4charlie]

Description

• Introduced a UTXO ranking parameter consolidationRank (set to 10 for now) as consolidation threshold.
• Added additional algorithm into SelectUTXOs to trigger consolidation on every outTx.
• Consolidation happens only when the resulting number of UTXOs (under TSS) is greater than 10, allowing a buffer of 10 incoming UTXOs created by cross-chain contract call (or donation) on Bitcoin.
• When consolidation happens, each outTx will be able to consolidate up to 19 (20 - 1) UTXOs.
• Reverted UTXO DustOffset back to 2000 for Zetachain mainnet.

Closes:

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/btc_signer.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]

Looks legit to me