feat: add OrcaRouter as a first-class LLM provider

[dulcestentaciones2920-debug]

What

SQLBot's model management lets users pick an LLM provider from the built-in supplier list (frontend/src/entity/supplier.ts) and connect it with just an API key. This PR adds OrcaRouter to that list as a first-class, named provider — mirroring how the existing OpenAI/DeepSeek entries are wired — instead of making users route it through the generic "自定义 / Generic OpenAI Compatible" fallback.

OrcaRouter is an OpenAI-compatible AI gateway built for both models and agents. Like OpenRouter, it exposes a provider/model namespace across many models — but it also combines adaptive routing, automatic failover, zero-markup inference, observability, guardrails, and agent-tool governance behind the same endpoint. Adding orcarouter as a first-class provider means SQLBot users can use that stack directly, without treating OrcaRouter as an anonymous custom base URL. It also runs gateway-level, zero-trust security for AI agents on the same endpoint — screening every prompt/response and governing every tool call on a default-deny basis, with no application code changes.

Changes

• frontend/src/entity/supplier.ts — new OrcaRouter supplier entry (id 16): base URL https://api.orcarouter.ai/v1, temperature default arg, and a curated model_options preset (orcarouter/fusion, orcarouter/fusion-flash, orcarouter/fusion-mini, orcarouter/auto, plus cross-provider models such as deepseek/deepseek-v4-pro, openai/gpt-4.1, qwen/qwen3.5-plus, google/gemini-2.5-pro, anthropic/claude-sonnet-5). All IDs are verified live against OrcaRouter's /v1/models.
• frontend/src/i18n/{en,zh-CN,zh-TW,ko-KR}.json — supplier.orcarouter → "OrcaRouter" (brand name kept in Latin across all locales, consistent with DeepSeek/OpenAI).
• frontend/src/assets/model/icon_orcarouter_colorful.png — provider icon (96×96 RGBA), matching the existing icon convention.
• README.md / docs/README.en.md — OrcaRouter added to the "Supported LLM Providers" table (OpenAI Compatible).

Verification

• vue-tsc -b — no type errors.
• eslint on touched files — clean.
• vite build — succeeds; the new icon is bundled as icon_orcarouter_colorful-*.png.
• L3 live test against the added provider path — POST https://api.orcarouter.ai/v1/chat/completions with model orcarouter/fusion returned HTTP 200 with a valid completion and usage metadata; a streaming request with orcarouter/fusion-flash also returned 200 with SSE chunks ending in [DONE].

Notes

The supplier registry is a pure frontend list — adding an entry requires no schema/migration changes, and ModelListSide.vue / ModelForm.vue pick it up automatically.

I'm an engineer on the OrcaRouter team.

Discord: discord.gg/YEubt8enRA · X: https://x.com/OrcaRouter