Fix not parsing full Deezer playlists

[freyacodes]

This allows lavasrc to process more than the first 25 tracks in a Deezer playlist.

This removes the API call to Deezer at /playlist/:id/tracks and uses the already fetched data from /playlist/:id instead. It appears that the former is paginated, returning 25 results, whereas the latter returns the full dataset without pagination.

Here is a playlist you can use for testing: https://www.deezer.com/en/playlist/11958416461?host=5617782001&deferredFl=1

The above playlist yielded 243/260 tracks in my testing with this patch.

[topi314]

the reason I opted for the /playlist/{id}/tracks endpoint was because the /playlist/{id} endpoint only returns partial tracks

we should instead implement the actual pagination for the /playlist/{id}/tracks endpoint

(it seems to only miss the isrc but it would be nice to have that)

[freyacodes]

In that case this is a trade-off between not getting ISRC or doing an additional 12 requests (in this case). I suppose the latter is acceptable

[freyacodes]

After messing around, I realise that we don't actually need to page through the list:

https://api.deezer.com/2.0/playlist/11958416461/tracks?limit=1000

So then I just need to revert this change and add the request parameter

[topi314]

lol, is 1000 the upper limit?
I can't find any docs on it, playlists could possibly have more songs than this right?

[freyacodes]

1.000 is not the upper limit. For the code I chose 10.000 as an arbitrary number

[topi314]

that is rather interesting lol