Colossus: visualize token/Broken-until-cleared tracking mechanic

[Splinter714]

Split off from #33.

Problem

Some colossus segments use a token-tracking mechanic (e.g. Daktadae's Head is "Broken until cleared" via tokens), and this isn't visualized on the card yet.

Desired

Add a visual representation of token/clear-state tracking on affected segments, consistent with how HP pips and Broken/Destroyed badges are shown elsewhere on the card.

Key files

• src/components/Adversaries/GameCard.jsx (renderExpandedColossus)
• src/components/Adversaries/colossi.json (Daktadae's Head as the reference case)

[Splinter714]

Re-triaged to blocked: same reason as #96 — the token-tracking visualization should be built against the post-#107 card structure (nested vs. separate-segment-cards), not the current one, to avoid rework. Will re-triage once #107 merges.

[Splinter714]

#107 has landed. Colossus display now supports two modes via a global toggle (Info panel → "Colossus display": Nested / Segments):

• Nested (default): unchanged — one card per colossus, segments listed inside it.
• Segments: each segment renders as its own standalone GameCard, styled like a regular adversary stat block (difficulty hex badge, ATK diamond badge, weapon pill, individually-clickable HP pips). Segment cards share a synthetic groupName (colossus: <baseName>) so EntityColumns' existing section-grouping keeps them visually adjacent — no new grouping mechanism was needed.

Data/structure notes relevant to token tracking:

• useEntityGroups.js expands a colossus's single entity-group entry into N pseudo-group entries (one per segment instance, keyed ${baseName}::${segmentKey}) when colossusDisplayMode === 'segments'. All pseudo-groups reference the same underlying colossus instances array/id — there's no separate per-segment token/instance state, so anything token-related still needs to key off the single colossus instance id, not the segment pseudo-group.
• GameCard gained segment (segment definition) and segmentKey (HP-tracking key, e.g. ikeri-arm-1 for multi-count segments) props. When set alongside item.isColossus, it renders via the new GameCard/ColossusSegmentCard.jsx instead of the nested view.
• Segment HP is unchanged in shape: instances[0].segmentHp[segmentKey] (a marked-count, not a boolean array), same in both display modes.
• Also fixed a pre-existing bug: segmentHp updates were routed to the group template instead of the instance (INSTANCE_FIELDS in useAdversaryState.js was missing 'segmentHp'), so HP pip clicks silently failed to persist in the nested view. Fixed now in both modes.

This should have what's needed to re-triage token tracking against both display modes. Not implementing this issue — just leaving the breadcrumb per the batch triage workflow.

[Splinter714]

Re-triaged to green: #107 has landed with the info needed (see breadcrumb comment above) — segment HP/data structure is settled for both display modes. Token tracking should key off the colossus instance id (not the per-segment pseudo-group), consistent with how HP pips/Broken badges already work. No remaining open question.