fix: timeout for process.exec

[vedranjukic]

Description

Fixes the process.exec timeout not being respected. When a command like sleep 5; echo 'hello' is executed with timeout=2, the timeout error is only thrown after the full 5 seconds instead of after 2 seconds.

Root cause: The SDK wraps user commands as sh -c "echo '<base64>' | base64 -d | sh", creating a process tree (outer sh → pipe → inner sh → sleep 5). When the daemon's timeout fired, cmd.Process.Kill() only sent SIGKILL to the outer sh process. The grandchild processes inherited the pipe file descriptors and continued running, causing CombinedOutput() to block until they exited naturally.

Fix (two parts):

1. Daemon (apps/daemon/pkg/toolbox/process/execute.go): Set Setpgid: true on the command so all child processes are placed in a new process group, then use syscall.Kill(-pid, SIGKILL) to kill the entire group on timeout. This ensures all descendant processes are terminated immediately.

2. SDK (libs/sdk-python/src/daytona/_sync/process.py, libs/sdk-python/src/daytona/_async/process.py): Added _request_timeout=http_timeout(timeout) to the execute_command() call in exec(), matching the pattern already used by execute_session_command(). This prevents the HTTP client from blocking indefinitely if the daemon-side timeout fails to respond promptly.

Documentation

• This change requires a documentation update
• I have made corresponding changes to the documentation

Related Issue(s)

This PR addresses issue #2602