[FE-20] Build PaginationControls component

[mftee]

Problem

Multiple list pages (documents, disputes, admin users) each need pagination but there is no reusable component. Without a shared component, every page would implement its own pagination logic inconsistently.

Proposed Solution

Create a reusable PaginationControls component inside frontend/module/components/pagination/.

Acceptance Criteria

• Accepts currentPage, totalPages, and onPageChange(page: number) callback props
• Renders Previous and Next buttons that are disabled at the first and last page respectively
• Renders up to 7 page number buttons — shows ellipsis (...) for large page ranges to keep the control compact
• Highlights the active page with a distinct visual style
• Calls onPageChange with the new page number when a button is clicked
• Does not render at all when totalPages is 1 or less
• Is fully keyboard accessible — all buttons are reachable via Tab and activated via Enter or Space
• All component files live inside frontend/module/components/pagination/

[shoaib050326]

@shoaib050326 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, I’ve reviewed the issue and the related flow. I’d like to work on this and can deliver a clean, well-tested implementation. Please assign it to me. Thanks!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @shoaib050326 to this issue.

[demilade18-git]

@demilade18-git has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hello,

I'd be happy to work on this issue.

I took some time to review the task and it looks like a good fit for my experience. I enjoy contributing to open-source projects, following established patterns, and making sure changes are well-tested and easy to maintain.

If the issue is still open, I'd appreciate the opportunity to contribute.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @demilade18-git to this issue.

[drips-wave]

Congratulations, @demilade18-git! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @demilade18-git: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @demilade18-git as part of the Stellar Wave Program's 5th Wave 🥳

😎 @demilade18-git: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.