[EVAL] API key from Env Var support

[daniel-lxs]

🧪 Evaluation PR for Testing

This is an automated test PR created for evaluation purposes.

---

Related GitHub Issue

Closes: #4337

Description

This PR adds support for obtaining API keys from the environment. A checkbox is added to each configuration that allows inputting an API key -- when checked, a given environment variable (eg, OPENAI_API_KEY, etc) is consulted for the key and the user is not required to provide one in the configuration. Env Var key is predictable but not editable.

Test Procedure

I tested this using VS Code run configurations, where the expected environment variable could be provided or omitted.

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).

A documentation update is advised, to describe environment variable usage to supply API keys.

• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Summary

Adds support for using environment variables for API keys across multiple providers, updates UI components to reflect this, and enhances testing and translation capabilities.

• Behavior:
  • Adds support for API keys from environment variables for providers like anthropic, glama, openrouter, openai, gemini, mistral, deepseek, unbound, requesty, xai, groq, chutes, litellm.
  • Updates validateModelsAndKeysProvided() to check for environment variable usage for API keys.
• UI Components:
  • Introduces ApiKey component to handle API key input and environment variable toggle.
  • Updates various provider components to use the new ApiKey component.
• Testing:
  • Adds comprehensive tests for environment variable integration and the ApiKey component.

[roo-code-dan]

Typo: MOONSHOOT should be MOONSHOT to match the environment variable name MOONSHOT_API_KEY. This typo will cause the constant to be named incorrectly throughout the codebase.

[roo-code-dan]

Using typo MOONSHOOT instead of MOONSHOT. This references the misspelled constant from constants.ts line 25. Should be API_KEYS.MOONSHOT to correctly reference MOONSHOT_API_KEY.

[roo-code-dan]

Using typo MOONSHOOT instead of MOONSHOT. This references the misspelled constant from constants.ts line 25. Should be API_KEYS.MOONSHOT to correctly reference MOONSHOT_API_KEY.

[roo-code-dan]

Missing useEffect to sync local state with prop changes. The useEnvVar state is initialized from configUseEnvVars but won't update if the prop changes later (e.g., when switching between provider profiles). Add:

useEffect(() => {
  setUseEnvVar(configUseEnvVars && apiKeyEnvVarExists)
}, [configUseEnvVars, apiKeyEnvVarExists])

[roo-code-dan]

Missing useEffect import. The suggested fix in the comment on line 34 requires importing useEffect from React.

[roo-code-dan]

Use this.log() instead of console.log() for consistency with the rest of the ClineProvider class. The class has a dedicated logging method that outputs to both the output channel and console.