feat: add command timeouts

[akintewe]

📝 Description

Add timeout enforcement to the commandExecutor utility to prevent long-running or infinite commands from hanging the backend. This is critical for security and reliability, as Rust compilation and testing can be resource-intensive. By setting a 30-second timeout, we ensure the backend remains responsive and aligns with the project's security requirements.

🚀 Changes Made

• ✅ Implement executeCommand function with 30-second default timeout
• ✅ Add CommandTimeoutError with clear error messaging
• ✅ Use setTimeout and child.kill() for timeout enforcement
• ✅ Capture stdout/stderr before timeout occurs
• ✅ Ensure proper cleanup of child processes to prevent resource leaks
• ✅ Add executeCommandWithTimeout convenience wrapper
• ✅ Create comprehensive TypeScript interfaces for type safety

🗂️ Files Added

apps/backend/src/utils/
└── commandExecutor.ts

🧪 Testing

• ✅ Tested timeout behavior with sleep commands (5s and 40s scenarios)
• ✅ Verified normal command execution remains unaffected
• ✅ Confirmed stdout/stderr capture works before timeout
• ✅ Validated proper process cleanup and resource management
• ✅ Test Result: Command timeout functionality is working correctly!

🔒 Security Benefits

• Prevents backend hanging from infinite or long-running commands
• Ensures responsive API even during heavy Rust compilation
• Protects against potential DoS scenarios
• Aligns with project's 30-second timeout security requirement

💡 Usage Example

import { executeCommand, CommandTimeoutError } from './utils/commandExecutor';

try {
  const result = await executeCommand('cargo', ['build', '--release']);
  console.log('Build successful:', result.stdout);
} catch (error) {
  if (error instanceof CommandTimeoutError) {
    console.error('Build timed out after 30 seconds');
  }
}

🔗 Closes

Closes #30

📋 Checklist

• Code follows project conventions
• No linting errors
• Timeout functionality tested and verified
• Proper error handling implemented
• Resource cleanup ensures no memory leaks
• TypeScript interfaces provide type safety

[salazarsebas]

LGTM