Algolia InstantSearch v5 Pagination Widget Migration: New limit and scrolling Parameters Required

When upgrading Algolia InstantSearch from version 4 to version 5, the pagination widget API changes: the new widget requires explicit limit and scrolling parameters, whereas v4 treated them as optional.

The goal is to update the pagination configuration so that the search result paging behaves identically to the v4 implementation while adopting the v5 widget.

Because backward compatibility is not guaranteed, developers must verify that the supplied limit and scrolling values produce the same page size and scrolling experience, and check for any subtle differences in user interaction.

What specific limit and scrolling settings should be used to match the v4 defaults?
How does the separation of page‑size and scrolling concerns in v5 affect the rendering or state management of the pagination widget?
Are there additional migration adjustments—such as CSS class names or event handlers—required to preserve the existing pagination behavior?