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

They were left included during the migration to meson to ensure that all
tests were still run, but now that we made sure they are, there's no
point in including that code in test coverage

We want the tests to explicitely fail if no case matched the given
parameters

When the authority is terminated by a fragment delimiter ('#') or by a
query delimiter ('?') we must not use any potential path delimiter found
later in the URL
Might solve #358

The previous code was fairly broken and wasn't allowing an existing
instance to be replaced. The stop/replace/start sequence was also
broken.
This tries to properly:
- Stop currently running background tasks that use libvlc
- Replace the instance when nothing is using it
- Restart what we stopped

It's worth noting that the fsFactories will be started when required and
don't need a manual restart.
We could do without forcing the parser & discoverer restart, but this
would cause any potentially running scan/discovery to be aborted and not
be restarted until the user explicitly asks for it

Fix #357

Fix #354

This way an application can still store a progress without knowing the
media duration
refs #354

Relying on a media instance means we can't use this code in a migration,
which we do.
While this only moves the problem to File's instances, the File table
is less likely to change than the Media one

Fix #348

And test it with another case for external media
Refs #348

refs #348

Which will store the number of external media assigned to a group
refs #348

These traces are behind a flag and are only explicitely enabled during
development. Using verbose means we also need to modify the unit tests
configurations

If the previous test failed, we didn't erase the database on purpose in
order to be able to ship it as an artifact for potential investigation
after the unit tests complete on the CI.
However for the database tests, it means that we will unconditionally
run all the mock database commands on an existing database, which
usually fails before the actual test begins

External media shouldn't be included in the network stream history, and
checking for a known type is not the correct way of checking for the
import type for quite a while now.

The value is not shared so we might as well pass a const ref directly

To abide by the unwritten convention of prefixing the trigger with the
entity type it concerns

Fix #353

The cached state wasn't updated, which was causing some tests to fail if
the media wasn't fetched back from the database

Fix #349

This is way too verbose in most cases