feat: bitcoin account types

[darioAnongba]

Add support for remaining Bitcoin account types.

This PR removes validation checks for the decoding of the address as the address is never decoded and simply displayed as returned from the Snap. Removes bech32 dependency.

p2sh is a shortcut for p2wpkh-p2sh (nested segwit).

• Fixes: https://consensyssoftware.atlassian.net/browse/NNT-329

[ccharly]

I think we should still validate the address formats here. We could use bitcoin-address-validation package for this, however, given that we are using 1 single struct, it will be hard to make sure the address is valid for the given type.

So maybe we should have 4 different structs instead (similarly to BtcP2wpkhAccountStruct, we would have BtcP2shAccountStruct, etc...), allowing us to strictly check the address is valid for the account's type?

WDYT?

[darioAnongba]

The address should not be validated because for the extension, the address is a string. For example if the Snap tells you that your address is fooBar then that's your address. you can't decide that you don't agree with the Snap. You can very well imagine that we are using petnames instead of bech32 addresses in the Snap and it would be acceptable.

Knowing the address encoding is not needed in the business logic. We can validate length though.