FOUR-28487: Fix pagination per-page selection resetting on page navigation

[eiresendez]

Issue & Reproduction Steps

On the Cases list (/cases), selecting 50 items per page resets to 15 after navigating to the next/previous page, even though the table still renders 50 items.

1. Go to /cases.
2. Select 50 per page in the paginator.
3. Click next page, then previous page.
4. Observe the per‑page selector resets to 15.

Solution

• Keep the pagination component’s selected per‑page value in sync with the parent via a new perPage prop and reactive watchers.
• Remove forced remounts (:key="dataPagination.page") so pagination state is not reset on page changes.
• Pass perPage from parent paginated views to the Pagination component.

How to Test

1. Open /cases.
2. Select 50 per page.
3. Navigate to the next page and back.
4. Confirm the per‑page selector remains 50 and the table still shows 50 items.
   Optional: Repeat on other screens that use the same pagination component (e.g., case detail tables and launchpad tables) to ensure the selection persists.

Related Tickets & Packages

• FOUR-28487

ci:deploy

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[vladyrichter]

QA server K8S was successfully deployed https://ci-a5b3603e34.engk8s.processmaker.net

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube