fix(ramps-controller): omit crypto from payment methods requests

[amitabh94]

Explanation

GET /v2/regions/:region/payments is scoped to provider and region. The API already ignores crypto, but RampsService.getPaymentMethods still put the token on the query string.

That made Cloudflare treat each token as a distinct cache object for the same payment list, so token changes on the input screen missed CDN and hit origin.

This stops sending crypto on that request. assetId stays on the method for caller cache keys and staleness checks. Quotes still send crypto and still use Cache-Control: no-store.

References

Related to on-ramp-api quote RegionCache work (explicit-provider fast path). Client-side companion to reducing /payments CDN fragmentation.

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

Made with Cursor