feat: Add API key support for Ollama Embedder Provider

[roomote]

Related GitHub Issue

Closes: #8737

Roo Code Task Context (Optional)

This PR was created with assistance from Roo Code to address the feature request.

Description

This PR adds API key support to the Ollama Embedder Provider, enabling authentication with remote protected Ollama instances. The implementation:

• Adds an optional ollamaApiKey parameter to the CodeIndexOllamaEmbedder class
• Includes Bearer token authentication in all API requests when an API key is provided
• Updates the configuration system to securely store and retrieve the Ollama API key
• Adds a UI field for entering the API key in the Code Index settings
• Maintains full backward compatibility with local Ollama instances that don't require authentication

Key implementation details:

• API keys are stored securely using VSCode's secret storage API
• The authentication header is conditionally added only when an API key is present
• Follows the same patterns as other embedder providers (OpenAI, Gemini, etc.) for consistency

Test Procedure

Manual Testing Steps:

1. Open the Code Indexing settings in the extension
2. Select "Ollama" as the embedder provider
3. Enter a base URL for your remote Ollama instance
4. Enter an API key in the new "Ollama API Key" field
5. Test the connection to verify authentication works
6. Verify that local Ollama instances still work without an API key

Automated Tests:

• Added 8 new test cases in src/services/code-index/embedders/__tests__/ollama.spec.ts
• Tests cover authentication scenarios, error handling, and backward compatibility
• All tests pass successfully

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

This is primarily a backend change with minimal UI impact. The only visible change is the addition of an API key field in the Code Index settings when Ollama is selected as the embedder provider, which follows the same pattern as other providers.

Documentation Updates

• No documentation updates are required.
• Yes, documentation updates are required. The documentation should be updated to mention that Ollama embedder now supports API key authentication for remote instances.

Additional Notes

This implementation provides feature parity with other embedder providers by adding the requested API key support. The changes are minimal and focused, following existing patterns in the codebase to ensure consistency and maintainability.

Get in Touch

For any questions about this PR, please reach out through the GitHub issue comments.

---

Important

Adds API key support for Ollama Embedder Provider, enabling secure authentication with remote instances.

• Behavior:
  • Adds ollamaApiKey parameter to CodeIndexOllamaEmbedder for API key support.
  • Includes Bearer token in API requests if API key is provided.
  • Maintains compatibility with local instances not requiring authentication.
• Configuration:
  • Updates codebaseIndexProviderSchema and global-settings.ts to include codebaseIndexOllamaApiKey.
  • Uses VSCode's secret storage for secure API key storage.
• UI:
  • Adds API key input field in CodeIndexPopover.tsx for Ollama settings.
• Testing:
  • Adds tests in ollama.spec.ts for API key authentication scenarios.
• Misc:
  • Updates webviewMessageHandler.ts to handle API key storage and retrieval.

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

[roomote]

✅ Code Review Complete - No Issues Found

I've completed a thorough review of this pull request and found no issues that need to be addressed.

Review Summary

Strengths:

• ✅ Follows existing codebase patterns for API key handling (consistent with OpenAI, Gemini, Mistral providers)
• ✅ Comprehensive test coverage with 8 new test cases covering authentication scenarios
• ✅ Properly handles the optional nature of the API key (maintains backward compatibility)
• ✅ Uses Bearer token authentication correctly in all API requests
• ✅ Type definitions are complete and consistent across all layers
• ✅ Securely stores API keys using VSCode's secret storage API
• ✅ UI implementation follows the same pattern as other embedder providers

Implementation Quality:

• Code is minimal and focused on the specific feature
• No code duplication - reuses existing patterns
• Error handling is appropriate
• Documentation in PR description is clear and complete

This PR is ready to merge. Great work! 🎉