This means readers (publish-db) won't block writers anymore, the
download-results currently times out sometimes due to the lock
being held by publish-db.
publish-db: Use the sqlite3 backup API to copy the DB
This seems to be 100% slower, but it should be safer to do as
we don't just copy the file object without any locks, which
might yield an inconsistent state.
We copy the file in steps of 128 * 1024 pages, this allows the lock
to be released in between, such that other programs can write
to it. Currently, that is about 3 iterations.