fix: Handle relayed txs and errors in status screen

[usame-algan]

What it solves

Resolves #2023

How this PR fixes it

• Handles Relayed transactions in Status screen
• Listens to the TxEvent.FAILED event in order to show an error state and message

How to test it

1. Open a Safe
2. Queue a transaction that would fail
3. Execute the transaction via relayer (or any other method that will result in a TxEvent.FAILED event)
4. Observe the Status screen changing

Screenshots

Checklist

• I've tested the branch on mobile 📱
• I've documented how it affects the analytics (if at all) 📊
• I've written a unit/e2e test for it (if applicable) 🧑‍💻

[github-actions]

Branch preview

✅ Deploy successful!

https://success_screen_ui--walletweb.review-wallet-web.5afe.dev

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[usame-algan]

Relayed transactions don't have a txHash so the stepper looks kinda empty. We could think about either hiding it or showing something else there instead of saying "Your transaction"