fix: respect custom OpenRouter URL for all API operations

[roomote]

Summary

This PR fixes an issue where custom OpenRouter URLs were not being fully respected throughout the application. When users configured a custom OpenRouter endpoint, some operations (model retrieval, cost calculations, CSP headers) would still use the hardcoded official OpenRouter URL.

Problem

As reported in #8947:

• When a custom URL is set in OpenRouter configuration, model retrieval and cost calculations still interact with the official OpenRouter endpoints
• CSP headers were hardcoded to only allow connections to the official OpenRouter domain
• This affected users who need to use self-hosted, proxy, or third-party OpenRouter-compatible endpoints

Solution

This PR ensures that all OpenRouter interactions respect the custom URL configuration:

Changes Made

1. Image Generation API - Use configured instead of hardcoded URL

   • : Updated method to use custom base URL

2. CSP Headers - Dynamically include custom OpenRouter domain in Content Security Policy

   • : Extract and include custom domain in CSP headers for both production and development modes

3. Model Endpoints Fetching - Pass custom base URL to webview hooks

   • : Added parameter
   • : Pass to the hook

Testing

• ✅ All existing tests pass
• ✅ OpenRouter provider tests pass
• ✅ OpenRouter fetcher tests pass
• ✅ ClineProvider tests pass

Fixes

Fixes #8947

---

Important

Fixes issue where custom OpenRouter URLs were not respected across API operations, ensuring all interactions use the configured URL.

• Behavior:
  • Ensure all OpenRouter interactions use custom URL if configured, defaulting to https://openrouter.ai/api/v1 otherwise.
  • Update fetch calls in openrouter.ts to use baseURL from options.
  • Modify CSP headers in ClineProvider.ts to include custom OpenRouter domain.
• Components:
  • Update useOpenRouterModelProviders in useOpenRouterModelProviders.ts to accept baseUrl parameter.
  • Pass openRouterBaseUrl to useOpenRouterModelProviders in ApiOptions.tsx.
• Misc:
  • Fixes [ENHANCEMENT] When custom url is used in Openrouter, model retrieval and costs are still pointing to the official one #8947.

^{This description was created by for 24e00b6. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Code Review Complete

I've reviewed this PR and found no issues with the implementation. The changes correctly address the reported issue by:

1. ✅ Using the configured openRouterBaseUrl in the image generation API instead of the hardcoded URL
2. ✅ Dynamically extracting and including the custom OpenRouter domain in CSP headers for both development and production modes
3. ✅ Passing the baseUrl parameter through to the webview hooks for model endpoint fetching

The implementation properly handles:

• Fallback to the default OpenRouter URL when no custom URL is configured
• Safe regex extraction of the domain with appropriate fallbacks
• Consistent use of the custom URL across all OpenRouter API operations

All changes are well-structured and maintain backward compatibility.

Follow Along on Roo Code Cloud

[roomote]

No issues found.