FOUR-32395: Respect non-filterable request columns

[eiresendez]

Issue & Reproduction Steps

The fixed-scope request trays in Cases / My Requests expose the Status column filter even when saved search metadata marks that column as non-filterable.

Reproduction:

1. Open Started By Me, In Progress, or Completed under Cases / My Requests.
2. Open the Status column menu.
3. Confirm that statuses outside the tray's fixed scope are available.

Solution

• Update the request listing to respect filterable: false when rendering column filter popovers.
• Preserve sorting and filtering for columns whose metadata allows it.

How to Test

Automated validation:

• The RequestsListing Vue template compiled successfully.
• The companion package SavedSearchTest.php suite passed from ProcessMaker core: 10 tests, 32 assertions.

Manual verification:

1. Open Started By Me, In Progress, and Completed under Cases / My Requests and confirm that Status has no filter menu.
2. Open All Requests and confirm that the Status filter remains available.
3. Confirm that other sortable and filterable columns still expose their menus.

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-32395
• https://github.com/ProcessMaker/package-savedsearch/pull/676

ci:deploy
ci:package-savedsearch:task/FOUR-32395
ci:skip-build

[decisions-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

[eiresendez]

@nolanpro
This deploy-EKS job is failing, err: user is not authorized to run eks:DescribeCluster on pm4-eng. Please let me know if there’s anything I can do on my side; otherwise, could you please take a look so we can generate the QA server?

cc: @sanjacornelius

[nolanpro]

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