Content Drive: pagination buttons stay enabled while a page is loading, allowing duplicate requests

Problem Statement

The Content Drive pagination controls (next/previous page) remain clickable while a page request is already in flight. Clicking them again before the current request resolves fires additional, redundant requests for the same navigation action.

Steps to Reproduce

Video: content drive pagination buttons.mov

1. In Content Drive, navigate to a folder/search result with multiple pages.
2. Click the "next page" (or "previous page") button while the current page is still loading.
3. Click it again (or multiple times) before the request completes.
4. Observe multiple network requests fired, one per click, instead of the click being ignored/debounced while a request is in flight.

Expected vs Actual

Expected: pagination controls should be disabled (or clicks ignored) while a page request is in progress, so only one request is made per navigation action.

Actual: pagination buttons remain enabled during loading; repeated clicks fire additional requests.

Acceptance Criteria

• Pagination controls are disabled (or non-interactive) while a page request is in flight
• Rapidly clicking a pagination control while loading results in exactly one request, not one per click
• No regression to normal pagination behavior once a request completes

Parent Epic

#36814