fix: limit param in search is incorrect

[juanmigdr]

Explanation

According to the docs, we have been passing the incorrect limits to the API since the beginning, I have updated it to pass first instead of limit and added the Ondo exception that is added on the API side

References

https://consensyssoftware.atlassian.net/browse/ASSETS-2632

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
Changes request construction for the Token Search API and alters effective result sizes via new clamping logic, which could affect downstream token search UX and pagination expectations.

Overview
Fixes token search pagination by switching the Token API query parameter from limit to first in getTokenSearchURL.

Adds limit clamping to avoid oversized searches: regular queries cap at 50 results, while queries containing Ondo can request up to 500 (otherwise clamped back to 50). Tests are updated/expanded to assert the new parameter and clamping behavior, and the changelog records the fix.

^{Written by Cursor Bugbot for commit 33d7542. This will update automatically on new commits. Configure here.}

[juanmigdr]

@cursor update the assets-controllers changelog

[cursor]

I've successfully updated the assets-controllers changelog! Here's what I accomplished:

• Added a proper changelog entry in the "Unreleased" section under a new "Fixed" category
• Documented the token search API fix that changes the parameter from limit to first for correct pagination
• Included details about the new features: limit validation (max 50 results by default) and the special Ondo exception (up to 500 results for Ondo queries)
• Validated the changelog format using yarn changelog:validate to ensure it meets the project's standards
• Committed and pushed the changes to the fix/limit-in-search-is-incorrect branch

The changelog entry follows the project's "Keep a Changelog" format and provides clear information about the bug fix and its implementation details for future reference.

  

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.