PMMSimpleConfig rejects candles_config field sent by Dashboard, strategy never starts

Describe the bug
Deploying a PMM Simple bot via Dashboard's 'Deploy V2' succeeds at the Docker level (container starts, process runs), but the actual trading strategy fails to start due to a Pydantic validation error, leaving the bot silently idle.

To Reproduce

1. Deploy a PMM Simple controller via Dashboard
2. Container comes up and stays 'running', but /bot-orchestration/{name}/status via API reports status 'stopped' with empty performance/logs
3. Inside the container, logs_<bot_name>.log shows:
   hummingbot.core.trading_core - ERROR - Failed to start strategy v2_with_controllers: 1 validation error for PMMSimpleConfig
   candles_config
   Extra inputs are not permitted [type=extra_forbidden, input_value=[], input_type=list]

Expected behavior
Either Dashboard should not send a candles_config field for PMM Simple, or PMMSimpleConfig should accept it. Either way, the strategy should start and the failure should be visible in the Dashboard UI, not just buried in container logs.

Environment

• hummingbot/hummingbot-api:latest, image id 1a97c67ecc5f (pulled 2026-07-22)
• hummingbot/hummingbot:latest bot image
• hummingbot/dashboard:latest, image id fd28cc85ec0e (pulled 2026-07-22)
• Deployment: Docker Compose, Ubuntu VPS

Additional context
Docker container itself reports healthy/running (exit code 0), and GET /bot-orchestration/{name}/status returns status 'stopped' with no error_logs — the failure is only visible by reading the bot's log file directly inside the container. This mismatch between 'container running' and 'strategy actually active' makes failed deployments look successful in the UI.

Trace the Dashboard “Deploy V2” request through the bot-orchestration status endpoint and the PMMSimpleConfig validation reported in the container log. Reproduce the deployment and compare the submitted configuration with the fields accepted by PMMSimpleConfig. Done means the PMM Simple strategy starts successfully and a failed strategy is surfaced in the Dashboard rather than only in the container log.