Expose total for paginated APIs

[timrae]

Feature Request

Some Spotify APIs use a paginated response model. For example in the ArtistManager class, the search() and getAlbums() functions take a limit and offset parameter which can be used to specify the page number and size.

Unfortunately these functions do not expose the total number of items, so in general the developer doesn't know whether or not there are more items able to be read. In this case it could be necessary to make one api call more than necessary to ensure that all items have been fetched.

In these instances it would be useful to return the raw response data (which includes the .total member) instead of the .items data member, to allow the developer to optimize performance.

[scientific-dev]

The spotify-types, spotify-api.js and their documentation are outdated for a few functions. The updates will be made in the upcomming version which will take some time (probably more than a month).

[johnyvelho]

using user.getPlaylists() and would also be nice to have pagination metadata like .total, .next, etc.