mbsync / missing plugins: consider all metadata backends

[snejus]

This PR adds support for alternate metadata backends in the mbsync and missing plugins, allowing them to work with any metadata backend the items are tagged with instead of being limited to just MusicBrainz.

Key changes:

• Removed redundant albums_for_id and items_for_id methods.
• Updated album_for_id and track_for_id implementations to return a single album/track as their names suggest.
• Updated both plugins to use the above functions instead of MusicBrainz-specific ones.
• Updated missing plugin docs to make it clear that missing albums for artists can only be obtained for the musicbrainz metadata backend
  • This is possible with other backends but implementation was outside of this PR's scope.
  • Slightly simplified the existing implementation

The changes maintain backwards compatibility while enabling users to leverage metadata from sources like Deezer, Discogs or Bandcamp when syncing their libraries.

Note: this change came about because I'm working on making musicbrainz a separate plugin: this will be submitted in the next PR.

[wisp3rwind]

While I won't have time to review this in depth anytime soon, here's one thing that's unclear to me at a superficial glance:

• Removed redundant albums_for_id and items_for_id methods.
• Updated album_for_id and track_for_id implementations to return a single album/track as their names suggest.

Looking just at the changed code, it appears that albums_for_id could previously indeed return several candidates given a single search_id, whereas now only the first one is used (i.e. musicbrainz if available, else the first plugin match).

Maybe this makes sense (possibly, a given search_id is only ever expected to return a single result for a single service?), but I feel like it would warrant a code comment explaining why we potentially drop additional results.

[snejus]

Maybe this makes sense (possibly, a given search_id is only ever expected to return a single result for a single service?), but I feel like it would warrant a code comment explaining why we potentially drop additional results.

That's exactly my thinking - I have worked with all available metadata sources, and I'm yet to discover a case where a single ID yields more than one album / singleton. I will add a comment under these methods.