fix: increase e2e test step timeout on Windows to fix flaky CI

Windows CI runners with Git Bash have significantly more overhead for
shell startup and process execution. The 20-second per-step timeout was
frequently exceeded on Windows, causing flaky failures in tests like
"multi task with cache hits shows compact summary" where `[timeout]`
appeared instead of actual output. Increase to 60 seconds on Windows
while keeping 20 seconds on Unix.

https://claude.ai/code/session_01VzFJkUBQ9t6zTmH7ZJFXgt

Author: claude

crates/vite_task_bin/tests/e2e_snapshots/main.rs

@@ -17,8 +17,13 @@ use vite_path::{AbsolutePath, AbsolutePathBuf, RelativePathBuf};
 use vite_str::Str;
 use vite_workspace::find_workspace_root;
 
-/// Timeout for each step in e2e tests
-const STEP_TIMEOUT: Duration = Duration::from_secs(20);
+/// Timeout for each step in e2e tests.
+/// Windows CI needs a longer timeout due to Git Bash startup overhead and slower I/O.
+const STEP_TIMEOUT: Duration = if cfg!(windows) {
+    Duration::from_secs(60)
+} else {
+    Duration::from_secs(20)
+};
 
 /// Screen size for the PTY terminal. Large enough to avoid line wrapping.
 const SCREEN_SIZE: ScreenSize = ScreenSize { rows: 500, cols: 500 };