Fix case detail ALERTS/COMMENTS count filtering the case list instead of revealing attached alerts/comments

[davethegut]

Summary

Fixes #58.

Clicking the ALERTS/COMMENTS count in a case's detail view was wired through the same onFilter handler used for CREATED BY, so it set the case-list search query to the raw count (e.g. 15) instead of showing anything useful — the detail pane closed and the case list re-rendered filtered by that number.

Changes

• Root fix: FactCol (src/views/case-management/App.tsx) generalized from a hard-coded "filter" button (onFilter?: (q: string) => void) to a generic onClick/title pair, so each fact controls its own click behavior instead of every value being treated as a filter query.
• CaseDetailView's ALERTS/COMMENTS now call a new revealSection helper that expands and scrolls to the existing "Attached alerts"/"Comments" sections. Only enabled when there's actually content to show (context loaded and non-empty) — no dead buttons pointing at nothing.
• CREATED BY explicitly keeps its original filter-the-list behavior.
• Same fix applied to the case-list card (CaseCard): ALERTS/COMMENTS there are now always plain text — a raw count was never a meaningful list filter, so it's no longer rendered as a filterClick button.

Test plan

• npm run typecheck passes
• npm run lint passes
• Verified end-to-end in Claude Desktop via a locally-built .mcpb: clicking ALERTS/COMMENTS on a case now reveals the attached alerts/comments sections instead of filtering the case list; CREATED BY filtering is unaffected

[opauloh]

LGTM - desk tested