feat: support Bitcoin P2TR, P2WSH, P2SH, P2PKH address types

[ws4charlie]

Description

1. Currently we only support sending to P2WPKH address. Need to support P2TR/P2PKH/P2SH/P2WSH.
2. Currently we only support receiving BTC from P2WPKH address. Need to support P2TR/P2PKH/P2SH/P2WSH.

WIP:

• backport AddressTaproot type that fulfills the btcutil.Address interface
• add P2TR output
• add P2PKH output
• add P2SH output
• add P2WSH output
• read P2TR sender
• read P2SH sender
• read P2PKH sender
• read P2WSH sender

Closes:
1626
1627
1773

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/fee.go, zetaclient/bitcoin/fee_test.go, e2e/e2etests/e2etests.go, zetaclient/bitcoin/bitcoin_client.go, zetaclient/bitcoin/bitcoin_client_test.go, zetaclient/bitcoin/bitcoin_signer.go, zetaclient/bitcoin/bitcoin_signer_test.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]

Any difference with #1842?
The other one can maybe be closed then

[lumtis]

We have withdraw E2E tests. Just to make sure, there is no deposit tests to do because it has nothing to do with the wallet address format?

Needs #1953 merged to run the E2E tests

[ws4charlie]

We have withdraw E2E tests. Just to make sure, there is no deposit tests to do because it has nothing to do with the wallet address format?

Needs #1953 merged to run the E2E tests

There is no deposit tests to do?
Yes, there is no deposit tests. The incoming tx's output format (to TSS address) has already been defined long long ago and never changed.

Then what was added for incoming txs?
What added in the PR is the ability to parse 4 more additional types of depositors' address: P2TR P2WSH P2PKH P2SH. This incurred a bit code refactor and the intx sender address parsing method GetSenderAddressByVin which is covered in unit tests and live tests.

[kevinssgh]

Overall looks good, left some comments.

[lumtis]

Looks good to me. Thanks for addressing the comments.
Added suggestions for some additional tests

[kevinssgh]

Looks good