Description:
When the data_source filter is updated to archived, scrolling fails to load additional PipelineRun results. The onScroll callback does not trigger the next-page request because the Tekton Results client reads nextPageToken, while the API returns next_page_token. As a result, the next-page callback is never created, and pagination stops after the first page.

Steps to Reproduce:

1. Open the PipelineRun list page.

1. Set the data_source filter to archived.

1. Scroll to the bottom of the list.

1. Observe that no new results load.

Actual Result:
Pagination does not progress beyond the first page; new results are not loaded when scrolling.

Expected Result:
Scrolling should correctly fetch subsequent pages using next_page_token, and additional results should load continuously.

Root Cause:
Mismatch between expected field (nextPageToken) in the client and actual field (next_page_token) returned by the API, preventing pagination from initializing the next-page callback.

Impact:
Users cannot browse archived PipelineRuns beyond the first page, limiting navigation and data visibility.

Proposed Fix:
Update the pagination logic to read next_page_token from the API response and correctly create the next-page callback.