[Tracking Issue] Code Refactor

[Flouse]

• Is this line unused?
  Originally posted by @Flouse in feat(rgbpp-sdk/btc): btc rgbpp transactions #26 (comment)
  fixed in fix(rgbpp-sdk/ckb): RawTransaction to CKBComponents.RawTransaction #38

• Review the logic of BTC transaction fee calculation
  https://learnmeabitcoin.com/technical/transaction/size/#weight

• BTC Replace by Fee (RBF) feature: Allow a BTC transaction to be replaced with a higher fee #82

• replace all void 0 to undefined
  Originally posted by @ShookLyngs in feat(service): throw service error with context #149 (comment)

[ShookLyngs]

Enabling the RBF feature (allowing transactions to be replaced) is easy, but how to sign and send the same transaction again is a problem. The issue is that when we got the UTXOs to construct a transaction, we got them from the btc-assets-api. And once the transaction is constructed, it no longer contains some required properties for us to "reverse" the whole construction process and convert a Transaction to a PSBT.

For example, how does the process know which output (vout) in the transaction can be altered in order to pay more fees? And besides, what's the dust limit for each output? Since outputs can be normal UTXOs (dust_limit=1,0000) or RGBPP UTXOs (dust_limit=546)._limit=546).