feat: session-persistent list filters (issue #3789 Deliverable B)

[weimiao67]

What changed

Filter selections on the list pages now persist across client-side navigation for the duration of the session, so returning to a list (e.g. via a breadcrumb) keeps the user's filters — and selected fiscal year — applied. Filters are intentionally lost on browser refresh / new tab (in-memory Redux) and cleared on logout.

Approach: extend the session-scoped sessionUISlice (introduced in Deliverable A) with a listFilters sub-state keyed by page, and add a useListFilters(page) hook exposing a useState-compatible API (object or functional-updater form) so the existing *FilterButton / *FilterTags sub-components keep working unchanged. All six list pages source their filters (and fiscal year, where applicable) from the slice instead of local useState. Logout reset reuses A's single extraReducers hook.

Pages: Agreements, CANs, Budget Lines, Portfolios, Projects, Procurement Dashboard.

Key pieces:

• sessionUISlice listFilters — per-page default shapes copied verbatim from each page's original useState; selectedFiscalYear persisted alongside filters where the resolved query blends both. setListFilters / setListFiscalYear / resetListFilters actions; buildPageState is the single deep-clone source for init + reset.
• useListFilters(page) — filters / setFilters / selectedFiscalYear / setSelectedFiscalYear, plus changeFiscalYear which atomically resets the page's filters and sets the new FY (one shared code path for all FY-aware pages).
• CANFilterButton — fixed a reference-equality budget check to compare by value.

This is Deliverable B of the issue and stacks on Deliverable A (#5995) — the PR is based on the A branch so the diff shows only B's changes. Rebase to main once A merges.

Issue

#3789

How to test

1. Go to any list page (e.g. Portfolios), apply a filter → open a detail page → navigate back. The filter is still applied.
2. Change the fiscal year on a list, navigate away and back → the FY selection persists.
3. Fiscal-year change resets filters consistently across Agreements, CANs, Projects, and Portfolios (a filter valid in one FY is not carried into another).
4. On CANs, apply a budget-range filter, reopen the filter modal, drag the slider back to the full range, and Apply → the budget filter is cleared (not retained).
5. Refresh the browser → filters clear (in-memory only, by design). Log out → filters clear.

Verified locally by driving the running stack (apply → navigate → back → still applied; FY persists; refresh clears).

A11y impact

• No accessibility-impacting changes in this PR

No markup/ARIA changes; filter state moves from local component state to Redux with identical rendering.

Storybook

• N/A — change is page-specific or non-visual

Changes are in a Redux slice, a hook, and page/hook wiring — no src/components/UI/ component added or changed.

Definition of Done Checklist

• OESA: Code refactored for clarity
• OESA: Dependency rules followed
• Automated unit tests updated and passed
• Automated integration tests updated and passed
• Automated quality tests updated and passed
• Automated load tests updated and passed
• Automated a11y tests updated and passed
• Automated security tests updated and passed
• 90%+ Code coverage achieved
• Form validations updated

Notes for reviewers

• Behavior change: CANs and Projects now clear other filters when the fiscal year changes (previously CANs reset nothing and Projects cleared only the FY chip). This aligns with the product decision "changing FY still clears other filters" and makes all four FY-aware pages consistent.
• A follow-up commit in this branch addresses code-review findings (budget-clear bug, FY-reset unification, defensive selector chaining, dedup).

Links

• Depends on: feat: context-aware breadcrumbs (issue #3789 Deliverable A) #5995 (Deliverable A)