fix(trustlab): fix list filters — repeated query params, singular keys, toolkit/playbook date filtering

[kilemensi]

Description

What & why

Multi-value list filters serialised as comma-joined strings, so any value containing a comma (e.g. Nairobi, Kenya) was split and corrupted the backend query. This switches to repeated query params, consolidates date-range/query-param logic into shared, tested utilities, and standardises filter params to singular names end to end (filter.type === URL param === API param), matching the CMS filter config.

⚠️ Behavioural / contract changes

• All four lists' filter URLs change (reports years→year, months→month, reports→report). Stale bookmarked / multi-select links silently reset — accepted trade-off.
• toolkits & playbooks date filtering was completely broken (front-end sent year/month, API read years/months) and now works.
• opportunities location filter is now exact (equals/in); search now matches title OR location.
• pageExtensions tightened to page.* so co-located *.test.js files stop being collected as phantom API routes.
• Adds DB indexes on title (all four) + location (opportunities) — triggers an index build on deploy.

Verified

• 177 unit tests (Jest), lint, format all green.
• Run against live data: comma values match exactly; equals is exact (substring → 0); toolkit/playbook year=2025→0 vs year=2026→5 (filter now honoured); repeated multi-value params; title+location search; renamed report slug filter.

Known limitations (out of scope)

• Filter-bar UI doesn't reflect the URL, and the first-interaction anomaly remains (results restore, controls don't).
• No search on toolkits/playbooks yet (so no search parity there).
• Indexing covers title/location but not the date / createdAt / slug fields the range filters scan.

Test plan

• pnpm jest --filter=trustlab (177 passing)
• pnpm lint:check / pnpm format:check
• pnpm build --filter=trustlab
• Live API smoke for all four lists (filter, multi-value, search, bookmarked URL)
• Browser confirmation of client-side URL→results restore

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Screenshots

N/A

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation

[kilemensi]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 🎉

Reviewed commit: 2937a8f433

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".