fix(spotify): use search.maxResults configuration for search limit

[realkalashnikov]

Changes

• Decoupled the Spotify search query limit parameter from the playlistLoadLimit configuration.
• Refactored the search() method in src/sources/spotify.ts to retrieve and use this.nodelink.options.search.maxResults (defaulting to 10) instead of this.config.playlistLoadLimit.

Why

The official Spotify text search query API calls (/v1/search) were incorrectly inheriting the playlistLoadLimit configuration, which is designed solely to limit the amount of pages loaded when fetching Spotify Playlists, Albums, or Artists.

If a user configured a low playlistLoadLimit (e.g., 1 or 2 to avoid massive playlist ingestion and API rate limits), text-based Spotify searches (spsearch) would yield only 1 or 2 results instead of the expected search result list count.

Standardizing on search.maxResults fixes this text search limitation bug and aligns the Spotify source's text search behavior with all other sources (such as Apple Music, Tidal, and Deezer) in NodeLink.

Checkmarks

• The modified endpoints have been tested.
• Used the same indentation as the rest of the project.
• Still compatible with LavaLink clients.

Additional information

This bug caused Discord music bots using NodeLink to always return only a single track choice when users searched by keyword using the Spotify source, if playlist loading restrictions were active.

[Copilot]

Pull request overview

This PR fixes Spotify text search result limiting by decoupling it from playlistLoadLimit and instead using the global search.maxResults option, aligning Spotify search behavior with other NodeLink sources.

Changes:

• Refactored SpotifySource.search() to use this.nodelink.options.search.maxResults (defaulting to 10) for search result limits.
• Removed the prior coupling to this.config.playlistLoadLimit for Spotify search requests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.