The verbosity is always forwared as is to the logger, storing it has no
purpose since it's never read

We are starting to have too many things protected by the same lock.
Marking these 2 members as const means we can safely assume they do not
need to be protected

Not doing so means we are losing the user's input when stopping, or when
replacing the libvlc instance.

Don't force a parser recreation when replacing libvlc instance since the
instance isn't cached anymore. The next run will simply use the updated
instance
refs #361

This can greatly simplify replacing an external instance by removing the
need to manually stop all parsers before recreating them, for a rather
limited run-time cost

Stop the background tasks as the main locked operation, use the unlocked
helpers for restarting after the instance has been replaced
Should fix #361

VLCInstance has its own mutex to protect the instance, so we don't need
to hold the media library mutex while probing the instance class
refs #361

refs #361

Fix #323

Fix #359

Fix #300

This is not critical but if we chain multiple migrations we might end up
recreating the backup table while it still exists

Since some thumbnails might be in a broken state, let's regenerate
everything

This now monitors insertion to the cleanup table and batches them.
This allows us to filter what kind of thumbnails we want to cleanup (ie.
only the owned ones) and stop relying on potentially invalid assumptions
when computing the thumbnail path.
refs #350

refs #350

refs #350

Which will store what thumbnail needs to be removed from disk, to remove
the use of a deletion based on a sqlite trigger
refs #350

We're starting to have rather long triggers which don't fit in 2048
characters.

Should fix #356

AutoDeleteAfterUpdate and ShareThumbnail were testing the exact same
thing, so remove one of them

Most of those are not used yet but will be if we ever need a new
version of an index/trigger.
For now they are used as assert only

Which will mark parameters only used in asserts as unused, instead of
spamming the logs with warnings

Some recent changes seem to cause a build failure in release mode, which
isn't tested in any configuration

So we at least check that we can provide a QueryParameter and that it's
correctly interpreted

It's never read from