Consider always running the analyzer in "dry run" mode first

[sschuberth]

Sometimes the analyzer is taking quite long, like a two-digit minute duration, which could be too long for the impatient user to get a quick first overview of that's contained in the repository.

So the idea is to always run what the AnalyzerCommand calls --dry-run first and return early from the backend some brief statistics, like the found definition files and package managers, for the UI to populate e.g. this card early: