The contact and reservation registry synchronization job should handle more than 1000 changes

[SandGrainOne]

Description

The current implementation of the synchronization job with the contact and reservation registry handles just a single list of changes. This limits the job at 1000 persons being updated/created per execution. We want this to be changed to that the job can run for longer to handle more changes.

Additional Information

No response

Tasks

• Implement a loop around the current implementation where it will continue to fetch more changes as long as there are changes to get
  • The assumption is that we can see if a page has 1000 persons and assume that this means there are more pages to retrieve. This is unless there is a more explicit paging mechanism provided by the API. If so use that instead.
  • Store the last change number every iteration so that we can continue from last success if we need to restart the job

Acceptance Criterias

• The sync job iterates over all available changes instead of only the 1000 we get on first request