review: only bridge model component spans across a numeric version boundary

The boundary-padded containment still matched variant suffixes: "gpt-4o" matched "gpt-4o-mini" because gpt-4o is a clean component prefix. Distinguish a version boundary from a variant one: a shorter id matches a longer one only when the component immediately after the matched span is purely numeric (a version/date). So "claude-sonnet" -> "claude-sonnet-4-5" and "sonnet" -> "claude-sonnet-4-20250514" still match, but "gpt-4o" -> "gpt-4o-mini", "gpt-4" -> "gpt-4-turbo", and bare fragments like "4-5" do not. Extends the table tests accordingly.