[Feature]: Handle RBF Received Activity

[catch-21]

Describe the problem

Currently, when a Received Activity is replaced (RBF) an error toast is displayed, the existing Received Activity turns red has it has been replaced from the mempool, and a new Received Activity appears for the new transaction.

Describe the solution

There is no need for the toast error. The existing Received Activity could be updated to include the new transaction details when RBF is detected.

Additional context

[JeanlChristophe]

@aldertnl any advice here?

[JeanlChristophe]

Closing the ticket, feature included

[catch-21]

@JeanlChristophe I don't see any logic changes to handle this scenario. FYI this is not a design issue, it is a technical one. It is to detect when the tx associated with your Received Activity has been replaced (RBF) rather removed from mempool without replacement.