fix: Validation for spending limits

[usame-algan]

What it solves

Part of #2067

How this PR fixes it

• Pass in validation to TokenAmountInput and make the Max field optional
• Remove amount validation for spending limits
• Adjust spending limit replacement UI when values don't change
• Update Remove Guard title text

Other changes

• Resets the amount to an empty string instead of 0 when switching tokens

How to test it

1. Open a Safe
2. Overwrite an existing spending limit but don't change any values
3. Observe no Max button visible
4. It should be possible to type in a larger amount than is available for a given token
5. Observe no strike-through values on screen
6. Change the reset time
7. Observe the old reset time is striked through and has its original value and not the relative time

Screenshots

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