[BUG] Bash commands ignore BASH_DEFAULT_TIMEOUT_MS and hang indefinitely

## Environment

• Platform (select one):
• [ ] Anthropic API
• [x] AWS Bedrock
• [ ] Google Vertex AI
• [ ] Other: <!-- specify -->
• Claude CLI version: 1.0.56 (Claude Code)
• Operating System: Linux (WSL2 - Windows Subsystem for Linux)
• Terminal: zsh

## Bug Description
Bash commands ignore the BASH_DEFAULT_TIMEOUT_MS configuration and hang indefinitely, but work correctly when
timeout is manually specified in the command.

## Steps to Reproduce

1. Set environment variables: export BASH_DEFAULT_TIMEOUT_MS=5000 and export BASH_MAX_TIMEOUT_MS=10000
2. Configure ~/.claude/settings.local.json with timeout settings
3. Execute any bash command: ejecuta: gh repo list
4. Command hangs for ~2 minutes without timeout
5. Execute same command with manual timeout: ejecuta ese comando con timeout de 5s
6. Command executes immediately

## Expected Behavior
Bash commands should automatically use the default timeout of 5000ms as configured in environment variables and
settings files.

## Actual Behavior

• Commands without manual timeout specification hang indefinitely (~2 minutes)
• Commands with manual timeout specification work immediately
• Default timeout configuration is completely ignored

## Additional Context

• Tested with multiple commands (gh, aws, git, echo)
• Problem persists across Claude Code restarts
• Configuration verified in both environment variables and settings.json
• Using Bedrock with CLAUDE_CODE_USE_BEDROCK=1
• Workaround: Always specify timeout manually