fix: use MultiSendCallOnly 1.3.0 for older Safes

[iamacook]

What it solves

Resolves #2498

How this PR fixes it

MultiSendCallOnly only exists as of version 1.3.0. Older Safes (<1.3.0) now use MultiSendCallOnly 1.3.0 by default.

How to test it

Bulk execution

1. On a <1.3.0 Safe queue multiple transactions.
2. Click bulk execute from the queue.
3. Observe no crash.

Simulation

1. Simulate a multiSend transaction on a <1.3.0 Safe.
2. Observe no error when simulating (not related to simulation result).

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

[schmanu]

Good catch!

[francovenica]

Looks good to me

I was able to reproduce the issue in current staging.

I tried the same in a safe 1.1.1 in the PR and the issue doesn't happen anymore
I tried safes 1.3.0 and there no issues there