feat(byok): show qodercli custom providers in the model selector

[luoxuanzao]

Summary

• SDK-spawned qodercli sessions run the CLI in its "sdk" runtime mode, where custom providers configured in the CLI (self-defined base URLs) stay disabled unless QODER_SDK_CUSTOM_BASE_URL_BYOK=1 is present — so their models never reached Qoderian's model selector. The plugin now sets that opt-in for every spawned CLI at the shared spawn boundary (createCustomSpawnFunction), which covers the runtime probe, cold-start queries and every chat turn.
• Models the CLI reports with source: "custom" now group under Custom in the selector, next to the existing BYOK (user) ones.
• The catalog stays a plain live fetch: requesting custom providers by id (outerProviders) makes the server reject the live request with a 400, so that path is deliberately not used (comment added to prevent a regression).

Verification

• npm run typecheck
• npm run lint
• npm run test — 165 suites / 3540 tests pass
• npm run build
• npm run release:check — Release 1.0.10 is ready
• npm run audit:prod — 0 vulnerabilities
• Tested affected qodercli behavior against a real CLI: with a CLI-configured custom provider (openai-compatible, local base URL) qodercli --list-models lists its models, a plain prompt routes through the provider, and the SDK session reports them as source: custom
• Real-app check: the runtime probe in a live vault lists the custom models and the composer's selector shows them under Custom

Safety

• No credentials, private vault content, internal URLs, or personal paths are included
• User-visible changes are documented in CHANGELOG.md

Co-authored-by: QoderAI (Qwen 3.8 Max) qoder_ai@qoder.com