fix: Hide confirmation dialog if set via setTxFlow

[usame-algan]

What it solves

Part of #2067

How this PR fixes it

• Uses the browser native confirmation dialog
• Prevents navigation if user cancels
• Adds another option to setTxFlow to bypass confirmation dialog

How to test it

1. Open a Safe
2. Create new transaction
3. Navigate away
4. Observe no confirmation dialog
5. Click on Send tokens
6. Try to navigate away or close the window
7. Observe a confirmation dialog

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://confirmation_dialog--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]

We might be able to use our own confirmation dialog but we need to figure out how to do it all in one callback that we can await and throw if necessary. The previous approach of rendering another component depending on a local state didn't work with blocking the router event.

[usame-algan]

This caused MUI errors because Tooltips can't also contain a title.

[katspaugh]

Neat.