If the discoverer signals its completion right after the parser, we'd
ignore the parser completion, causing the test to hand until it times
out.

This flag is solely about the parser completion, make it clearer

When tearing down MediaLibraryWithDiscoverer, we end up stopping the
parser from the media library destructor (not the
MediaLibraryWithDiscoverer one) which causes the vptr to be updated to
the MediaLibrary one. This will cause the regular getParser overload to
be used if the discoverer thread asks for a parser when stopping.
By explicitly stopping the discoverer from the test class, we ensure the
proper vptr gets used until the discoverer thread joins

Register & unregister the FsHolder callback from the discoverer thread
instead of the thread that starts the discoverer.
If the FsHolder callback is registered from enqueue(), we lock the
discoverer mutex, then the fs holder mutex, and will lock in the
opposite order when the callback is invoked

We are adding new tasks, not necessarily flushing whatever was already
scheduled

It has an updated wine version, among other things

This image has an updated base and a much more recent wine version
installed (7.0 vs 5.x)

Otherwise there's a slight window in which the parser could signal a
task completion while the operation hasn't been accounted for in the
scheduled counter

Refs #412

refs #412

Fix #398

It appears gcc11 exposes the std::thread type but can't take a pointer
to method, which is the only way we care about for now.
Fix #408

Refs #408

Fix #410

refs #410

If the application tries to fetch information about a media from an MRL
that points to a playlist, we should tolerate it and just return a
nullptr media
Fix #407

This means that the media library is still initializing, and the parser
will be started a bit later. Since the first thing it will do is to
restore all unfinished tasks, the tasks will still execute.
Fix #404

This will help exhibiting the issue in #404 and future similar issues

Fix #403

When using pkg-config with >= 0.11.0 it wouldn't detect the library as
available unless we include the patch level explicitly in the generated
.pc

Fix #402