GitLab

Refs #29

refs #29

refs #29

Since we can now analyze disc files
refs #29

refs #29

But keep the existing fallback in place since it's likely that the files
won't have their type known in this code path

Instead of always passing Unknown

And just use medialibrary::IFile::Type instead
We soon will also expose the file type directly, and we don't want to
duplicate the type again, so just use the regular file type for
fs::IFile as well

Which doesn't test something in particular, but which tries to reproduce
a more real-life like setup, as opposed to most test cases which only
have a single folder being discovered.
This would have caught the regression caused by !392 and fixed in !395

This also drops the --testdir parameter which was never used since it
was introduced

Since the function isn't recursive anymore, we are probably better off
skipping to the next folder in the discovery stack rather than aborting
the discovery entirely.
This is a good indication that our tests are a bit too simplistic

subFolder is a const& and can't be moved, so let's not pretend that's
what we're doing

So that the logs don't show banned folders as being discovered

This simplifies the code and allows us to centralize the IO error
checks, which were causing the discovery to be aborted even though there
was just a single directory that wasn't readable
Fix #307

Fix #124

And let meson display the logs in case of errors

So it matches the associated header

Just run the tests with Debug verbosity and let meson print out the logs
if the test fails

So we can extract the value from gitlab

So we can always have the code coverage information available

Since the addEntryPoint task is prioritized, scheduling a discovery will
add the new entrypoint to database before the currently running
discovery completes.
Fix #302

Which will be used to replace discover by addEntryPoint + reload
refs #302