fix: remove Ollama template-based tool support gate

[RomneyDa]

Summary

• The Ollama provider was checking the model template (via /api/show) for a .Tools placeholder to decide whether to pass tools to the API
• This silently stripped tools for newer models (e.g. qwen3.5:9b) whose templates don't yet include .Tools, even when toolSupport.ts or explicit config said the model supports tools
• Removed the templateSupportsTools check entirely — if options.tools is non-empty, the upstream (capabilities.tools from config or toolSupport.ts heuristic) already decided the model supports tools

Test plan

• Configure an Ollama model (e.g. qwen3.5:9b) and verify tools are passed to the API
• Verify models that don't match toolSupport.ts heuristics still don't receive tools

[continue]

Documentation Review

No documentation updates needed for this PR.

Reason: This is an internal bug fix that makes the existing documented behavior work correctly. The documentation already instructs users to explicitly set capabilities: [tool_use] when auto-detection fails (see Ollama provider docs and Model Capabilities guide).

This PR fixes the code to properly honor those explicit capability settings for Ollama models—the user-facing configuration and recommended workflow remain unchanged.

[continue]

Test Coverage Review

This PR introduces new logic where capabilities.tools can explicitly override the template-based tool detection in Ollama. The following test cases should be added to core/llm/llms/Ollama.test.ts:

Suggested Test Cases

1. capabilities.tools = true overrides template detection: When capabilities.tools is explicitly true, tools should be included in chatOptions even if templateSupportsTools is false.

2. capabilities.tools = false overrides template detection: When capabilities.tools is explicitly false, tools should NOT be included even if templateSupportsTools is true.

3. capabilities.tools = undefined preserves existing behavior: When capabilities.tools is not set, the existing templateSupportsTools !== false logic should apply.

Example Test Structure

describe('_streamChat tool capability handling', () => {
  it('should include tools when capabilities.tools is explicitly true', () => {
    // Set capabilities.tools = true, templateSupportsTools = false
    // Verify tools are included in chatOptions
  });

  it('should exclude tools when capabilities.tools is explicitly false', () => {
    // Set capabilities.tools = false, templateSupportsTools = true  
    // Verify tools are NOT included in chatOptions
  });

  it('should use templateSupportsTools when capabilities.tools is undefined', () => {
    // Set capabilities.tools = undefined, templateSupportsTools = true
    // Verify tools ARE included (existing behavior)
  });
});

These tests would provide regression coverage for the bug this PR fixes and ensure the capability override precedence logic works correctly.

---

Automated test coverage check

[cubic-dev-ai]

No issues found across 1 file