Feature: allow withdrawal of unconfirmed transactions held in a static address

Right now, a transaction to a static address requires three confirmations before it can be withdrawn.

This could cause issues if the fee is (far) too low and the transaction cannot be RBF'd. The transaction could get stuck for a long time and remain unusable until confirmed. This could be a common scenario when chain fees suddenly rise.

My request is to allow unconfirmed transactions to be used for withdrawals. This would enable the transaction to be CPFP'd and become usable.

Start by tracing the withdrawal path for transactions sent to static addresses and locate where three confirmations are required. Read how unconfirmed transactions and CPFP are handled, then define the validation and safety cases for allowing withdrawal before confirmation. Done means the intended unconfirmed transaction can be withdrawn and CPFP'd without breaking existing confirmation behavior.

Written by the indexing model from the issue text.