This is a too big hammer and doesn't motivate to fix things. This was
required for leaky ring projects, but with that problem gone, we can
require adi projects to fix issues.
A rather small reviewbot just made for one thing: check maintenance
release requests. They are much easier to handle: they are only created
on locked projects, so there is no waiting required. Just checking
and if it's broken, the request can be declined.
Extract the writing of the susetags content into a new script that
also creates a yaml file which package comes from what directory.
This information is used in repochecks.py to run findfileconflicts
and installcheck as repo_checker.pl used to
Implement a new command that takes a target project and one of its
staging projects and will run the checks against that project (including
delete requests) and if all is fine approves all reviews selected in
that staging.
This is to be used as part of the staging pipeline (and has been tested
with Factory's staging projects)
