fix: allow non-owner spending limit benficiaries to transact

[iamacook]

What it solves

Resolves #1561

How this PR fixes it

Non-owner spending limit beneficiaries can now create and execute transactions according to their limits.

How to test it

1. Add a non-owner as a spending limit beneficiary to a Safe.
2. Switch to the spending limit beneficiary
3. Observe that it is possible to create and execute transactions spending limit transactions with the associated token.

Screenshots

[github-actions]

Branch preview

✅ Deploy successful!

https://spending_limit_beneficiaries--webcore.review-web-core.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}

[katspaugh]

A very solid approach! Scoped to the Send token modal.

[francovenica]

Looks good to me

Checked that you can only access the send funds functionality.
Only the token you have set in the spending limits are listed in the token list selection
Only the option to use spending limit (the radiobutton) is selected in the form
I wasn't able to do any other action with the former owner, which is the expected behavior.

Notes:
Some nish functionalities could be considered for this, like the "Send" button that shows in the assets table when you hover the assets row, or the "Send Again" functionality that you can use from the tx details in the tx history, but I'd assume those require a lot of extra validations. So I'm ok leaving those out and just allow the user to use the "New transaction" button as the only way to send funds

[iamacook]

Notes: Some nish functionalities could be considered for this, like the "Send" button that shows in the assets table when you hover the assets row, or the "Send Again" functionality that you can use from the tx details in the tx history, but I'd assume those require a lot of extra validations. So I'm ok leaving those out and just allow the user to use the "New transaction" button as the only way to send funds

Thank you for the recommendations. I will file issues accordingly.

[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}