Update response schemas to match the latest API version

[InputUsername]

ListenBrainz silently changed their response schemas, this PR addresses those changes (as reported in #12).

• user/{user_name}/playing-now:
  • Add UserPlayingNowPayload::playing_now;
  • Add UserPlayingNowListen::playing_now;
  • Remove `UserPlayingNowListen::{user_name, inserted_at, recording_msid}.
• user/{user_name}/listens:
  • Change the type of UserListensListen::inserted_at from String to i64.
• stats/sitewide/artists:
  • Remove StatsSitewideArtistsPayload::time_ranges;
  • Add StatsSitewideArtistsPayload::artists;
  • Remove StatsSitewideArtistsTimeRange;
  • Remove StatsSitewideArtistsArtist::artist_msid.
• stats/user/{user_name}/artist-map:
  • Change the return type of Client::stats_user_artist_map from Result<StatsUserArtistMapResponse, Error>
    to Result<Option<StatsUserArtistMapResponse>, Error>.
• users/{user_list}/recent-listens:
  • Remove Client::users_recent_listens;
  • Remove UsersRecentListensResponse;
  • Remove UsersRecentListensPayload;
  • Remove UsersRecentListensListen;
  • Remove UsersRecentListensTrackMetadata;
  • Remove examples/users_recent_listens.rs.

[shymega]

@InputUsername I'll review this tomorrow evening after I get back from my job interview.

[InputUsername]

@shymega perfect, thanks! And best of luck with your job interview 😄

[shymega]

@InputUsername This all looks fine to me, I think we should make it clear in bold that it's a breaking change release, given a fair amount of return types have been modified, but other than that, excellent! 💯

[shymega]

@shymega perfect, thanks! And best of luck with your job interview smile

Thanks! It went great, last time it didn't go so well (virtual, and it was mostly my fault), but this time they said my professionalism, body language, and questions/answers were vastly improved, so fingers crossed!

[InputUsername]

@shymega

@InputUsername This all looks fine to me, I think we should make it clear in bold that it's a breaking change release, given a fair amount of return types have been modified, but other than that, excellent! 💯

Thanks! It definitely makes sense to indicate the breakage more clearly (even though it's not technically required), so I've added a note to the changelog.

Thanks! It went great, last time it didn't go so well (virtual, and it was mostly my fault), but this time they said my professionalism, body language, and questions/answers were vastly improved, so fingers crossed!

That's great, hoping for the best 🤞

[shymega]

All good, much better to present it as a breaking change.