Fix a race that can cause hydra-queue-runner to ignore newly added builds

As @dtzWill discovered, with the concurrent hydra-evaluator, there can be multiple active transactions adding builds to the database. As a result, builds can become visible in a non-monotonically increasing order, breaking the queue monitor's assumption that build IDs only go up.

The fix is to have hydra-eval-jobset provide the lowest build ID it just added in the builds_added notification, and have the queue monitor check from there.

Fixes #496.

Created by  Eelco Dolstra  on July 21, 2017
S2NXJOJE3V7PTXHA2HAHA5BUSNJRHZNXBWK7KSWTPGISWKXYMJDQC
Change contents