Revert Fire Pass model id to the router path

The previous pass "aligned" model-resolver.ts to
accounts/fireworks/models/kimi-k2.5-turbo — the per-token model path —
to match the connector catalog's default. That was the wrong direction:
Fire Pass subscription traffic routes exclusively through
accounts/fireworks/routers/kimi-k2p5-turbo (see docs.fireworks.ai/firepass),
and the entitlement does not attach to the per-token id. Existing agent
rows already pointed at the router id, so validateConnectorModelSelection
rejected every dispatch with "does not allow model
'accounts/fireworks/routers/kimi-k2p5-turbo'" and the CEO stopped running
entirely.

Put the router id back in model-resolver.ts (the enabled-pool source of
truth), and bring the two catalog defaults in line so a freshly-seeded
Fire Pass connector also ends up on the router id. The per-token
`fireworks` connector keeps the `models/...` default since that path
bills per token and genuinely targets the per-model endpoint.

src/shared/connector-catalog.ts

@@ -236,9 +236,9 @@ const API_KEY_ENTRIES: ConnectorCatalogEntry[] = [
     provider: "fireworks-firepass",
     label: "Fireworks Fire Pass",
     description: "Fireworks Fire Pass — subscription bundle. Same FIREWORKS_API_KEY.",
-    defaultModel: "accounts/fireworks/models/kimi-k2.5-turbo",
+    defaultModel: "accounts/fireworks/routers/kimi-k2p5-turbo",
     auth: { type: "api_key", envKey: "FIREWORKS_API_KEY" },
-    notes: "Covers Kimi K2.5 Turbo only; other Fireworks models still bill per-token.",
+    notes: "Fire Pass uses the dedicated router id accounts/fireworks/routers/kimi-k2p5-turbo documented at docs.fireworks.ai/firepass.",
   },
 ];