feat(openai): add setting to disable native tool calling

[roomote]

This PR attempts to address Issue #10368. Feedback and guidance are welcome.

Summary

Adds a new user-facing setting openAiDisableNativeTools in the OpenAI Compatible provider settings that allows users to explicitly disable native tool calling (function calling) for models that do not support it.

Problem

DeepSeek-R1 and similar models do not support native function calling (tool calling), but the OpenAI Compatible handler in Roo Code sends native tools by default, causing 400 errors. As noted by @supuwoerc, model names are impossible to exhaustively list, especially for self-trained models or proxies.

Solution

1. Added openAiDisableNativeTools setting to the provider settings schema
2. Modified OpenAiHandler.getModel() to:
   • Respect the new user setting when enabled
   • Also expanded DeepSeek reasoner detection to include deepseek-r1 pattern (in addition to existing deepseek-reasoner)
   • When native tools are disabled (either by user setting or model detection), the extension falls back to XML tool protocol
3. Added UI checkbox in OpenAI Compatible settings to toggle this feature
4. Added translations in all 18 supported locales

Changes

• packages/types/src/provider-settings.ts: Added openAiDisableNativeTools to OpenAI schema
• src/api/providers/openai.ts: Modified getModel() to handle the new setting
• webview-ui/src/components/settings/providers/OpenAICompatible.tsx: Added checkbox UI
• webview-ui/src/i18n/locales/*/settings.json: Added translations for 18 locales

Testing

• All existing OpenAI provider tests pass (48 tests)
• TypeScript compilation passes for packages/types, src, and webview-ui

Closes #10368

[roomote]

Rooviewer   See task on Roo Cloud

Review complete. No issues found.

The implementation correctly adds a new openAiDisableNativeTools setting that allows users to explicitly disable native tool calling for models that don't support it (like DeepSeek-R1). The changes follow existing patterns and properly address the issue.

• Type schema updated correctly
• Handler logic properly disables native tools when setting is enabled or DeepSeek reasoner detected
• UI checkbox follows existing patterns
• All 18 locale translations added
• Test coverage added for all getModel() scenarios

Previous reviews

• ac0c694: Review #1

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[supuwoerc]

@roomote A test case failed during execution in cicd, preventing the PR from entering the ready state.

[roomote]

Fixaroo   See task on Roo Cloud

Investigated CI failures - they were infrastructure-related (flaky tests/timeouts), not code issues. Added test coverage for the new openAiDisableNativeTools setting (6 new tests, all 54 tests pass locally).

_{View commit | Revert commit}

[supuwoerc]

@mrubens @cte @jr
Could you check if this PR can be merged? Thanks.

[hannesrudolph]

@supuwoerc We will be removing the XML logic shortly.

Keeping two tool calling architectures massively increases complexity. Every fix, every feature, every tool-related issue forces Roo to reason about two completely different execution paths. That slows development, increases bugs, and makes it harder to move Roo forward. It also guarantees that XML users would slowly get stuck with an increasingly outdated experience as improvements land only in the native path.

https://blog.roocode.com/p/sorry-we-didnt-listen-sooner-native