FOUR-33159 POC Performance issue when open the columns configuration in saved search

[devmiguelangel]

Issue & Reproduction Steps

FOUR-33159 POC Performance issue when opening the column configuration in a saved search

Solution

Fixes variable loading for saved searches by separating available-column pagination from process-variable pagination.

• Loads all available columns before fetching process variables.
• Prevents duplicate and active columns from appearing.
• Adds bounded caching for saved-search and screen-derived columns.
• Fixes collection column discovery and object-based data handling.
• Falls back to screen variables when MySQL raises sort-memory error 1038.
• Updates Storybook mocks and interactions for the new pagination metadata.
• Adds regression coverage for pagination, filtering, caching, collection data, and fallback behavior.

Related Tickets & Packages

https://processmaker.atlassian.net/browse/FOUR-33159
https://github.com/ProcessMaker/package-savedsearch/pull/694

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.

ci:package-savedsearch:FOUR-33197

[decisions-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube