This was making the runner accept job with no tags, which is not the
same as accepting jobs without the priority tag. This would have caused
random unrelated user jobs to be picked by that runner, without having
any of the other tags such as the architecture or the gpu in runs on.

What already happens, without picking untagged jobs, is that jobs
without a priority get picked by any of the priority queues, as long as
the job has other tags and these other tags do match what the runner
has.

This is undesirable behaviour long-term, but very nice to have for
allowing a smooth transition into using this wrapper; see the README
part of this commit for more details.