fix: don't over-poll Spending Limits data

[iamacook]

What it solves

Reduces eth_call requests

How this PR fixes it

The length of the modules array is checked instead of the array itself when requesting spending limit details in useLoadSpendingLimits.

useAsync linting changed the safe.modules length dependency in favour of safe.modules. This caused the increase of eth_call requests as a new instance of the Safe info is returned every poll due to the loading flag in useSafeInfo.

How to test it

Open a Safe with spending limits enabled and observe a reduced number of eth_calls when compared to prod.

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