feat(provider): sync ThreatBook Router model catalog

[stephamie7]

Summary

• make ThreatBook-cn-llm use the configurable Router Console model catalog as the authoritative source
• synchronize active model names, prices, price versions, and tiered pricing
• remove the automatic /v1/models fallback and keep chat API keys out of catalog requests
• store Router Console catalog sessions separately for test and production origins
• refresh the catalog when the Flocks model page is refreshed

Scope

• Flocks-only changes; flocks-router is unchanged
• no Kafka-related changes and no standalone Router provider

Verification

• backend Router catalog tests: 11 passed
• frontend related tests: 28 passed
• frontend production build: passed
• Ruff checks: passed
• deployed locally and verified HTTP 200
• without a test Router session_token, the catalog returns 401 and Flocks safely serves its bundled fallback