Support loading global RooCode configuration from a fixed file path for automated environments

[codeMonkey-shin]

Hi,

I'd like to request an enhancement for the RooCode extension to better support automated and containerized deployments (e.g. VS Code Server on Kubernetes).

Problem:
Currently, RooCode configuration (such as LLM server host, model name, etc.) can only be set through the UI and exported/imported manually. This process is not suitable for automated workflows, where settings ideally need to be injected programmatically.

Feature Request:
Please provide an option for RooCode to automatically load its global configuration (settings JSON) from a specific file path (e.g. /etc/roocode/config.json or a user-defined path). The extension should read the settings from this file (if it exists) as the initial or global configuration.

Benefits:

Enables seamless, programmatic configuration via file mounts, ConfigMaps, or script automation.
Avoids manual UI interaction or import/export for each container/instance.
Improves compatibility with headless/cloud/devcontainer scenarios.
Example:
On VS Code Server startup, RooCode would check /etc/roocode/config.json (or another well-documented path) and apply the configuration automatically.

Thank you for considering this feature. It would make RooCode much more useful and flexible in modern development environments!