Progress bar stuck during archive import when adding new nodes

[GeigerJ2]

This was likely introduced by #6998 that removed batching the list of nodes before passing to the QB IN clause. The batching was likely also used for the progress bar update callback. Maybe there's another way to track the progress? Or we re-introduce the batching in such cases. It probably doesn't hurt, and the advantage of #6998—that not all callers of the QB have the responsibility to batch outside—remains.

Ping @edan-bainglass.