nightly-beda6fc7-ls198

CI Report:

https://ci-tests.linuxserver.io/linuxserver/beets/nightly-beda6fc7-ls198/index.html

LinuxServer Changes:

No changes

Remote Changes:

Add mbpseudo plugin for pseudo-release proposals (#5888)

Description

Adds the new mbpseudo plugin, that proactively searches for pseudo-releases during import and
adds them as candidates. Since it also depends on MusicBrainz, there are
some special considerations for the default logic (which is now a plugin
as well). However, at the very least it expects a list of desired names
of scripts in the
configuration, for example:

mbpseudo:
    scripts:
    - Latn

It will use that to search for pseudo-releases that match some of the
desired scripts, but will only do so if the input tracks match against
an official release that is not in one of the desired scripts.

Standalone Usage

This would be the recommended approach, which involves disabling the
musicbrainz plugin. The mbpseudo plugin will manually delegate the
initial search to it. Since the data source of official releases will
still match MusicBrainz, weights are still relevant:

mbpseudo:
    source_weight: 0.0
    scripts:
    - Latn

musicbrainz:
    source_weight: 0.1

A setup like that would ensure that the pseudo-releases have slightly
more preference when choosing the final proposal.

Combined Usage

I initially thought it would be important to coexist with the
musicbrainz plugin when it's enabled, and reuse as much of its data as
possible to avoid redundant calls to the MusicBrainz API. I have the
impression this is not really important in the end, and maybe things
could be simplified if we decide that both plugins shouldn't coexist.

As it is right now, using both plugins at the same time would still
work, but it'll only avoid redundancy if musicbrainz emits its
candidates before mbpseudo, which is why I modified the
plugin-loading logic slightly to guarantee ordering. I'm not sure if you
think this could be an issue, but I think the musicbrainz plugin is
also used by other plugins and I can imagine it's good to guarantee the
order that is declared in the configuration?

If the above is fulfilled, the mbpseudo plugin will use listeners to
intercept data emitted by the musicbrainz plugin and check if any of
them have pseudo-releases that might be desirable.