`413 Content Too Large` for `/v1/audio-features`

[ReubenFrankel]

For some reason, the Web API now allows the top tracks endpoint to return over 100 tracks for a user (observed for the long_term range). This has exposed a bug in the tap where it makes a request for the audio features of multiple tracks, the number of which now can be greater than the maximum allowed (100) - this either results in a 400 Client Error or 413 Content Too Large depending on how much this limit is exceeded by.