Properly get rid of all watcher jobs
Properly get rid of all watcher jobs

Our tests running via RunWithLocks strictly depend on no
watcher jobs interfering. Therefore they pause the watcher;
unfortunately, there still is a race: the watcher only checks
the pause status upon its invocation, but submits jobs later
in its run time. Therefore not only pause it (doesn't hurt),
but also add a filter to reject all its jobs, and then wait
for all running jobs to terminate.

Signed-off-by: Klaus Aehlig <4ce51de36d9068cd7db2eec1151e0f3f95419008@google.com>
Reviewed-by: Petr Pudlak <9d19625f8ee825a2c398462ed335cbcf98f79c32@google.com>

ganeti/ganeti,andir/ganeti,grnet/snf-ganeti,onponomarev/ganeti,bitemyapp/ganeti,andir/ganeti,yiannist/ganeti,grnet/snf-ganeti,leshchevds/ganeti,yiannist/ganeti,mbakke/ganeti,ganeti/ganeti,yiannist/ganeti,onponomarev/ganeti,mbakke/ganeti,ganeti/ganeti,leshchevds/ganeti,leshchevds/ganeti,bitemyapp/ganeti,mbakke/ganeti,andir/ganeti