Requirement for having only one valid unbonding transaction per Staking transaction

[KonradStaniec]

Description

Due to Babylon phased launch in which:

• In phase-1, stakers can lock their BTC on BTC chains and unbond them thanks to globally available covenant-committee
• In phase-2, stakers can transfer theirs stakes to Babylon chain by registering them via MsgCreateBTCDelegation with all required additional transactions.
  For each staking transaction there must exists only one valid unbonding transaction. If this invariant would be broken it would be possible for stakers to avoid slashing during unbonding period

Fixes made to preserve this invariant

• Making phase-2 unbonding timelock compliant with phase-1 parameters- require exact amount of blocks for unbonding timelock #314
• Introducing different parameters for staking transactions based on their inclusion height in BTC chain. This why phase-1 staking transactions will be validated against the same parameters as during phase-1 - adr-37 parameters for btc light client ranges #310
• Enforcing that unbonding transaction always have version 2 - Enforce that unbonding tx always has version 2 #311, and releasing this fix in Babylon version v0.17.2 - https://github.com/babylonlabs-io/babylon/releases/tag/v0.17.2
• Releasing covenant signer program (operated by phase-1 covenant signers) with updated Babylon version - https://github.com/babylonlabs-io/covenant-signer/releases/tag/v0.2.13
• Releasing new staking api version with updated Babylon version - https://github.com/babylonlabs-io/staking-api-service/releases/tag/v0.3.8