Pagination issue in Extension updater

I couldn't reproduce locally, but we had several reports that the issue exists in practice. The missing part is probably that the update results are only stored in the cache, and not serialized. Therefore, if the cache job is flushed from the cache, the second page cannot be retrieved and the update job needs to be restarted.