feat: add BIP-431 (TRUC) support

[oleonardolima]

Describe the enhancement
As reported in #419 we don't have proper support for BIP-431 (TRUC) transactions, which have different specification/policy for what outputs/nVersion can be used/mixed together, see BIP-431.

As described in-depth on BIP-431, and mentioned here we need to support the following specification:

• Rule 1: A TRUC transaction signals replaceability, even if it does not signal BIP125 replaceability.
• Rule 2: Any TRUC transaction's unconfirmed ancestors must all be TRUC. Any descendant of an unconfirmed TRUC transaction must also be TRUC. fix(wallet): exclude unconfirmed v3 outputs from non-v3 coin selection #442

  NOTE: A TRUC transaction can spend outputs from confirmed non-TRUC transactions. A non-TRUC transaction can spend outputs from confirmed TRUC transactions.

• Rule 3: An unconfirmed TRUC transaction cannot have more than 1 unconfirmed ancestor. An unconfirmed TRUC transaction cannot have more than 1 unconfirmed descendant. CPFP Carve Out is not granted to TRUC transactions.
• Rule 4: A TRUC transaction cannot have a sigop-adjusted virtual size larger than 10,000 vB. Rule 4: A TRUC transaction cannot have a sigop-adjusted virtual size larger than 10,000 vB. #484
• Rule 5: A TRUC transaction that has an unconfirmed TRUC ancestor cannot have a sigop-adjusted virtual size larger than 1000 vB. Rule 5: A TRUC transaction that has an unconfirmed TRUC ancestor cannot have a sigop-adjusted virtual size larger than 1000 vB. #485
• [x][+] Rule[/+][-] Rule[/-] 6: An individual TRUC transaction is permitted to be below the mempool min relay feerate, assuming it is considered within a package that meets the mempool's feerate[+] requirements. it's not applicable, lmk if i'm mistaken[/+][-] requirements.

Use case

It allows users to properly build TRUC transactions, without the need for any workaround as mentioned here: #419 (comment) (specially L2s, such as: Lightning, Ark, ...)

Impact

• Blocking production usage
• Nice-to-have / UX improvement
• Developer experience / maintainability

Are you using BDK in a production project?

• Yes
• No
• Not yet, but planning to

Which backend(s) are relevant (if any)?

• Electrum
• Esplora
• Bitcoin Core RPC
• None / not backend-related (e.g. bdk_chain, bdk_core)
• Other (please specify): ____

Additional context

[oleonardolima]

I discussed with @yan-pi and decided to create this issue to track all the required specs/policy for BIP-431.