feat: BTC multisig use `sdk.AccAddress`

[RafilxTenfen]

• Update to use sdk.AccAddress instead of Public Key to identify BTC staker bech32 address
• Proto Changes
  • Add new ProofOfPossesionBTC
  • Update BTCDelegation to use staker address instead of bbn pk
  • Update BTCDelDistInfo to use staker address instead of bbn pk
  • Update BTCDelegationResponse to use staker address
  • Remove signer from MsgCreateBTCDelegation and replace bbn pk by staker addr
• Add WalletName to NodeConfig in e2e test

Ref https://github.com/babylonchain/pm/pull/38

Other PR's will be created to

• [x] Add e2e test with multisig #664
• [x] Add e2e test with fee grant #670
• [x] Update btc-staker https://github.com/babylonchain/btc-staker/pull/167
• [x] Update covenant-emulator https://github.com/babylonchain/covenant-emulator/pull/47

[SebastianElvis]

Thanks for the changes. One high-level comment is that I feel this PR does not complete the whole feature described in ADR-020, which seems to require two more PRs. So I would expect a base branch like this to collect the whole feature set before merging it to dev. This way, this PR is part of the feature and can be renamed to something like ADR-020: Replace Babylon Pubkey with Staker Address, ref.

Hmm given that this PR is rather self contained (unlike the pub rand commit one where we cannot stay on the status after reverting BIP32 for long), probably this PR is fine to be merged to dev?

[KonradStaniec]

One high-level comment is that I feel this PR does not complete the whole feature described in ADR-020, which seems to require two more PRs

From what I see, the only two prs missing are:

• test
• modifications in adjecent repo

If thats all imo we can merge it to dev.

Although lets wait with merging this at least till core meeting. My main concern is, that we would like to return to running devnets, and if we merge it now we would need:

• either run devnet from some past commit, which may be messy as we usually run devnets from top of the dev branch
• or quickly modify other programs for devnet to make sense.

[gitferry]

@SebastianElvis @KonradStaniec Makes sense. I thought we also needed to change pop in MsgCreateFinalityProvider, but I guess that is independent of this PR. Let's merge this PR to dev then when we are ready

[RafilxTenfen]

For the BTC staker, I will make a PR after the resolution of new requirements for BTC delegation creation on someone's behalf