Added pagination for getting event attendees in the dashboard

[maernest04]

PR for #2117

Problem

The EventAttendeesDashboard previously lacked pagination support, making it difficult to manage and view attendees for events with a large number of registrations. Furthermore, the dashboard was susceptible to race conditions and unnecessary network traffic when users interacted with the interface quickly, as there was no mechanism to cancel outdated API requests.

Solution

• Implemented Pagination: Introduced registrationsOffset state to track the current page and added "Previous" and "Next" navigation controls. The dashboard now fetches attendees in batches of 100.
• Added Request Cancellation: Integrated AbortController into the data-fetching hooks. This ensures that if a user navigates away or triggers a new fetch before the previous one completes, the outdated request is cancelled to prevent state inconsistencies.
• Enhanced API Functions: Updated getEventRegistrations and getEventRegistrationByRequestId in the SCEvents API utility to accept and respect AbortSignal.
• Improved UI Feedback: Added a pagination status indicator (e.g., "1–100 of 500") and ensured navigation buttons are appropriately disabled during loading or when at the boundaries of the list.

Files Changed

• src/APIFunctions/SCEvents.js: Updated API call wrappers to support request aborting and handle AbortError gracefully.
• src/Pages/Events/EventAttendeesDashboard.js: Implemented pagination logic, navigation handlers, and request lifecycle management with AbortController.

Screenshots

First Page

Second Page

[steeevin88]

did you test this?