In testing the scheduler systemd stuff, I realized there's a
conflict problem. When you install fedora-openqa-schedule on a
non-Docker openQA setup (i.e. directly onto an openSUSE system
running openQA), it replaces openQA's own openqa-webui.service
and openqa-worker@.service. Obviously we want to be able to
deploy the scheduler without doing that, so this moves all the
systemd services that are useful only on the host of a Docker
deployment into docker/. It also moves the instructions for
enabling them into the docker/README.md, which is clearly where
they belong anyway: this is part of deploying the Docker
openQA, not part of installing the scheduler at all.
This also removes the scheduler services' requirement for
openqa-webui.service, which I've always thought is bogus.
Nothing about the scheduler requires it to run on the same
system where openQA is running. At the moment it does need to
run on a box that shares /var/lib/openqa/factory/iso with the
one where openQA is running, but that's not quite the same
thing, and I'm trying to get rid of that requirement anyhow.