Implement keyset/cursor pagination for users list page

[Copilot]

• Understand the issue and current implementation
• Create KeysetPagination component for cursor-based pagination
• Create KeysetDataProvider for efficient database queries
• Update UserController to use keyset pagination instead of offset pagination
• Update views/user/index.php to support keyset pagination links
• Remove temporary redirect from actionIndex

Changes Made

This PR implements keyset/cursor pagination for the users list page to reduce MySQL load.

New Components:

1. components/KeysetPagination.php - Handles cursor encoding/decoding and URL generation for prev/next navigation
2. components/KeysetDataProvider.php - Data provider that uses indexed columns (rank, id) for pagination instead of OFFSET

Modified Files:

1. controllers/UserController.php - Updated actionIndex() to use KeysetDataProvider instead of ActiveDataProvider
2. views/user/index.php - Updated to render table manually with keyset pagination nav (prev/next buttons)

How Keyset Pagination Works:

• Instead of OFFSET n, uses WHERE rank > :lastRank OR (rank = :lastRank AND id > :lastId)
• This leverages database indexes for O(1) page navigation regardless of page depth
• Encodes cursor position as base64 JSON containing the key column values
• Supports bidirectional navigation (next/prev pages)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Redo users list page using keyset / cursor pagination</issue_title>
<issue_description>Offset pagination creates too much load on MySQL.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Redo users list page using keyset / cursor pagination #1206

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.