Add a full paginated library browser

[austin-smith]

Summary

Add a first-class, paginated library browser so users can navigate their Spotify collection without relying on search or the small set of items shown on the opening palette.

The library should cover:

• Liked songs
• Saved albums
• Followed artists
• Saved and followed playlists
• Recently played tracks
• Top tracks and artists, with short-, medium-, and long-term ranges

Library rows should participate in the same play, queue, save, action, and drill-down flows already used by search results.

Why

Spotuify currently surfaces a useful but intentionally small home snapshot. A full library makes the app practical for everyday browsing, especially when the user already knows the collection they want but not the exact search query.

Important behavior

• Load collections incrementally and preserve the user's position while more results are fetched.
• Avoid eagerly walking every page on entry; Development Mode quota is limited and shared across a developer's apps.
• Keep collection failures isolated where possible so one unavailable or rate-limited section does not make the entire library unusable.
• Preserve the existing rule that playlist contents are only offered when Spotify exposes them to the signed-in user.
• Make empty, loading, exhausted, rate-limited, and retry states clear.

Out of scope

• Podcasts, episodes, and audiobooks
• Recommendation-based discovery or editorial browse
• Playlist creation and editing

References

• Get User's Saved Tracks
• Get User's Saved Albums
• Get Followed Artists
• Get Current User's Playlists
• Get Recently Played Tracks
• Get User's Top Items
• Quota modes
• Rate limits