fix: update session after approval

[iamacook]

What it solves

DApp on wrong chain

How this PR fixes it

1. The session is now updated after approval with the chain of the Safe, and updated session returned accordingly.
2. As a precaution, if no active session or matching chainId exists, an error is now returned upon "wrong" request.

How to test it

1. Connect to Uniswap via native WC with a Safe on Gnosis Chain. Observe it immediately requesting chain switch.
2. Connect via native WC to a DApp that doesn't support the current Safe and try to transact, observing the "Unsupported chains." error.

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://wc_wrong_chain--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}