hermes - 💡(How to fix) Fix config priority: OpenRouter catalog overrides explicit custom provider [2 pull requests]

When a user explicitly configures model.base_url and model.provider: custom in ~/.hermes/config.yaml, switching to a model whose name matches an OpenRouter catalog entry causes Hermes to override the configured base_url and route the request to OpenRouter, completely bypassing the user's custom endpoint.\n\nSteps to reproduce:\n1. In ~/.hermes/config.yaml set:\n model:\n base_url: "https://api.minimaxi.com/v1"\n provider: "custom"\n default: "MiniMax-M2.7"\n2. Ensure OPENROUTER_API_KEY is set in ~/.hermes/.env\n3. Run: hermes chat -m MiniMax-M2.5\n4. Observe: requests routed to openrouter.ai instead of the configured base_url.\n\nExpected behavior:\n- Hermes should respect explicit config.model settings (provider/base_url/model_mapping) before consulting the OpenRouter catalog.\n\nProposed minimal fix:\n- In hermes_cli/models.py detect_provider_for_model(), honor config.model.provider/base_url mapping before calling _find_openrouter_slug.\n\nLogs/trace:\n- See examples in ~/.hermes/logs/ mentioning 'Failed to fetch model metadata from OpenRouter' and local skill docs in skills/autonomous-ai-agents/hermes-agent referencing the model-switch bug.\n\nImpact:\n- Medium (P2): can leak keys and silently route traffic to third-party provider; causes confusion and incorrect billing/authorization failures.