fix: quote request should not be sent of amount of token requested by the user is 0

[jpuri]

Explanation

Money account page updated transaction a few times, this change ensure that we get quote only of token amount requested is not 0.

References

Fixes https://consensyssoftware.atlassian.net/browse/CONF-1241

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Medium Risk
Medium risk: changes quote-refresh behavior and can prevent downstream quote/total updates if token amount detection is incorrect, though scoped to a simple precondition check.

Overview
Prevents unnecessary quote API calls by short-circuiting updateQuotes when all non-skipIfBalance required tokens have amountRaw === '0', while still allowing quoting when isMaxAmount is true (or when tokens are absent).

Adds test coverage for the new skip/allow conditions and documents the fix in the package changelog.

^{Reviewed by Cursor Bugbot for commit 6efd589. Bugbot is set up for automated code reviews on this repo. Configure here.}

[jpuri]

On money account page token / accountOverride can be updated few times. We need to ensure that quotes is not refetched unless user enters a non-zero token amount. Thus this change is made.

Another approach could be to change methods setTransactionConfig, 'setPaymentToken' to not refresh quote is amount of token requested is zero.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit cc70919. Configure here.}