[ENHANCEMENT] Specify API key for Ollama Embedder Provider

[BadCoder1337]

Technical Reference https://docs.ollama.com/cloud?utm_source=chatgpt.com#authentication

Problem (one or two sentences)

I'm able to specify ollama embedder base URL but not an API key.

Context (who is affected and when)

I run remote protected ollama instance and am unable to use it without SSH port forwarding.

Desired behavior (conceptual, not technical)

There should be a feature parity with generic providers.

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

I'm exploring a potential fix for adding API key support to the Ollama Embedder Provider and will open a PR to share progress

[roomote]

I've opened PR #8738 with my attempt at adding API key support for the Ollama Embedder Provider: #8738

The implementation adds:

• Optional API key parameter to the Ollama embedder class
• Bearer token authentication in all API requests when an API key is provided
• Secure storage of the API key using VSCode's secret storage
• UI field for entering the API key in Code Index settings
• Comprehensive test coverage for the new functionality
• Full backward compatibility with local Ollama instances

Most CI checks are passing, though there appears to be an integration test failure that may need investigation. Feedback and guidance are welcome!