[customer analytics] Accounts list tag chips aren't clickable to filter

Summary

Tag chips shown in the accounts list are rendered as static tags with no click handler, so clicking one does nothing — but users click them expecting to filter the list by that tag (a common source of dead-clicks). The fix is to make each chip clickable so it adds its tag to the existing tags filter, with a visible active state when already applied.

Part of #68887.

Details for coding agents

Root cause
TagsCell renders <ObjectTags tags={tags} staticOnly />. staticOnly makes ObjectTags emit plain LemonTag chips with no onClick — purely decorative. The filter machinery already exists (setTagsFilter(string[]) backing the Tags dropdown), it just isn't wired to the chips.

Proposed fix
In TagsCell, render individual LemonTags each with an onClick that reads the current tagsFilter from accountsLogic and dispatches setTagsFilter([...tagsFilter, tag]) (idempotent — skip if already present). Give a chip an active/primary style when it's already in the filter. No backend change. Keep click affordance consistent with LemonTag conventions.

References

• products/customer_analytics/frontend/components/Accounts/AccountsHogQLTable.tsx:138-143 (TagsCell)
• frontend/src/lib/components/ObjectTags/ObjectTags.tsx:52,102 (staticOnly → no onClick)
• products/customer_analytics/frontend/components/Accounts/accountsLogic.ts:193,238-241 (setTagsFilter action + reducer)

Start in products/customer_analytics/frontend/components/Accounts/AccountsHogQLTable.tsx at TagsCell, then read ObjectTags.tsx and accountsLogic.ts to trace staticOnly, tagsFilter, and setTagsFilter. Make each displayed tag clickable, skip tags already in the filter, and show an active style for applied tags. Confirm the existing Tags dropdown behavior remains unchanged.