chore(send): collaborative send

[theborakompanioni]

Enhance the collaborative send flow to improve reliability and UX by saving the last payment attempt, better error reporting, and minor refactors.
Tries to mitigate missing infos on failed attempts: joinmarket-clientserver does not provide good info about errors or other failures.
Flow:

• store payment attempt + utxos hash in session storage
• wait till taker operation ends
• if utxos hash changed, show a success message
• if utxos has did not change, show an error message with payment attempt details

Note:

• if a user did not start the taker operation in this session, no info can be shown and collaborative send flow just ends without any information at all - this is not good UX, but we cannot really do anything about it.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	76.1% (🎯 70%)	1137 / 1494
🔵	Statements	76.03% (🎯 70%)	1253 / 1648
🔵	Functions	66.53% (🎯 60%)	348 / 523
🔵	Branches	69.1% (🎯 60%)	783 / 1133

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
src/components/send/PaymentAbortDialog.tsx	66.66%	100%	33.33%	66.66%	33-36
src/i18n/locales/en/translation.json	100%	100%	100%	100%

Generated in workflow #3122 for commit 1568f41 by the Vitest Coverage Report Action

[parrth20]

edge case: if /docoinjoin succeeds but coinjoin_in_process never flips true, or flips too quickly before the session poll sees it, this can stay in “Starting collaborative transaction...” forever.

Maybe we should add a timeout/reset fallback here, or allow the stored attempt to move into the completion/ended state after some time.

[theborakompanioni]

Good observation. While that is certainly true, it complicates the code and might create even more problems. I will revisit and see what can be done. Maybe address in a follow-up.

[parrth20]

smoll UI nit: this is the success branch, but it still uses AlertTriangleIcon. Maybe CheckCircle2Icon would make the completed state feel less like a warning.