fix: source amount calculation ignores fee asset

[micaelae]

Explanation

The initial toQuoteResponseV2 assumes that the metabridge fee is always paid in the src asset. This causes the src amount to be incorrect when the amounts are added up (srcTokenAmount + fees)

Changes

• export assetIdsMatch util, which does a case-insensitive comparison of EVM assetIds and case-sensitive comparison for non-EVM
• filter fees by assetId in toQuoteResponseV2 to prevent inflating src.amount

References

Fixes https://consensyssoftware.atlassian.net/browse/SWAPS-4930

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
Touches quote amount coercion and sent/adjusted-return calculations shown to users; logic is localized but wrong matching would still misstate balances.

Overview
Fixes incorrect source amounts when V1 quotes are coerced to V2 by only rolling tx and metabridge fees into src.amount when the fee’s assetId matches the source asset (via new assetIdsMatch).

Adds and exports assetIdsMatch: exact match for non-EVM CAIP IDs; for EIP-155, compares case-insensitively. Replaces ad hoc .toLowerCase() comparisons in sumAmounts, calcSentAmount, calcIncludedTxFees, and calcAdjustedReturn so fee/asset alignment stays consistent across coercion and metadata math.

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