[Chore]: Introduce `Rbf` status for Emily deposits

[MCJOHN974]

Chore - Introduce Rbf status for Emily deposits

1. Description

We want to add Rbf status for Emily deposits. Now, all deposits updates should have optional field for previous transaction, and if it present, Emily set Rbf status for previous transaction

2. Why It's Necessary

It would allow bridge to handle rbf'd transactions properly.

3. Execution Checklist

• Emily now have Rbf status

• Deposit update now have optional field for previous transaction

• Emily return an error and don't do an update if previous transaction is not in Emily db

• Emily automatically set status of transaction to Rbf during deposit update if this tx was marked as previous tx

• Previous transaction field is allowed only for sidecar

• Previous transaction field is also stored in db and can be retrieved via GET deposits/

• (Optional) recursive query to get all hierarchy of rbf'ing

[Jiloc]

We should also add the update to emily-cron to the tasks. i.e. modify here:

sbtc/emily_cron/app/services/deposit_processor.py

Lines 97 to 101 in d2cf286

	DepositUpdate(
	bitcoin_txid=tx.bitcoin_txid,
	bitcoin_tx_output_index=tx.bitcoin_tx_output_index,
	status=RequestStatus.FAILED.value,
	status_message=f"Replaced by confirmed tx {confirmed_txid_in_group}",

Also, another approach would be adding a replaced_by_tx instead of previous_tx . The difference would be that we could have all transactions replaced of the same rbf chain mark the replaced_by_tx making the process super easy.
On the negative side, we would lose the exact order of the rbf chain on Emily, as all RBFd transactions (but I am not sure how helpful that would be). What do you think?