feat: Use fetcher in workflow history

[Assem-Uber]

Summary
Use new fetcher hook in the history page. This replaces old logic of useKeepLoadingEvents hook which depends on the render cycle completion to start fetching the next page. The new hook allows throttle query data updates and render once after few requested pages.

Changes

• Replace existing useSuspenseInfiniteQuery with the new fetcher hook
• Replace the existing useKeepLoadingEvents with usage for start/stop methods from fetcher
• Delete useKeepLoadingEvents as it is no longer used.
• Misc: Fix a type for header export button arg (it had extra fields than it needs)

Recording
Using custom buttons to validate start/stop/error of the fetcher on the history page.
The start/pause/error buttons are for testing purposes

Tested scenarios:

• Stop start manually using buttons
• Tested errors in API requests and handling retries
• Tested loading more by scrolling
• Tested recovering from errors by scrolling to the end of the page

Screen.Recording.2025-11-03.at.11.07.09.mov

Risks
If fetcher is problematic, loading more pages may not happen. Ending up with a partially fetched history.