fix: get Safe address on-chain for ZK creations

[iamacook]

What it solves

Resolves #2370

How this PR fixes it

This updates the @safe-global/safe-core-sdk to 3.3.5 as per requested which fixes Safe address prediction on ZK chains.

How to test it

Create a Safe on a ZK chain and observe the correct Safe address in the creation stepper/navigation link after indexed.

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

[francovenica]

Looks good.
The address shown during the safe creation process is the same as the safe after being created:

[francovenica]

@iamacook Since @schmanu requested a change I'll not pass the ticket to QA done yet. Let me know if that change requieres a re-test.

It was for a previous version