When there was a source commit on the bci repo, then the set of
packages changed, which likely means we need those changes to pass
the tests on the container release pipelines. So don't wait for 24h
but publish right away.
Also trigger on the oldest published state rather than the newest one
so that we do not need to wait another 24h per openQA failure to resume
publishing.
The goal is to publish the repo at most daily. Previously this was ensured
by simply running the bot only once a day. However, due to OBS and openQA
timing this was frequently attempted when either of those wasn't done yet,
which happened several times in a row. To not miss times when they align,
attempt publishing more often but skip a build if the previous publish was
recent enough.
Unfortunately TTM itself doesn't quite fit here due to the reasons outlined
in the code and the additional checks are not a good fit for adding it into
the go pipeline description, so write yet another OBS publishing bot!
For the initial test runs this is not triggered by timer runs yet.
