Rebuild vFrictionEvents as tiered view family (supersedes VENUS-227 shape)

Elazar directive (bs-mriqv6hg7ge follow-up, 2026-07-13-02:04, via pm-mars-cc) supersedes VENUS-227's single-view shape. Build tiered view family instead: vFrictionEvents, vFrictionEvents1w, vFrictionEvents1m (+ any other window tiers venus wants) each LIMIT 1000 (agent/LLM-consumption sizing, not display sizing) — plus a NoLimit twin per tier (vFrictionEvents1wNoLimit, vFrictionEvents1mNoLimit, etc.), unbounded, time-filter only, for when >1k rows genuinely needed. Same family/suffix naming convention across mars/venus/pluto/enamel so agents can query any project's friction views by the same pattern. Keep venus's existing category='toast' AND action='error-shown' predicate (VENUS-227 already verified this is the correct non-success filter for venus). Class-A DDL -> db-venus-cc. Update venus-commons.md Friction View section to the new family shape (supersedes the VENUS-227 write-up).