fix: set FORCE_COLOR=0 in e2e tests to prevent color output on Windows

On Windows CI, terminal color detection may behave differently, causing
ANSI escape codes to appear in snapshot output even with NO_COLOR=1 set.
Explicitly setting FORCE_COLOR=0 ensures colors are fully disabled.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: branchseer

crates/vite_task_bin/tests/test_snapshots/main.rs

@@ -181,6 +181,7 @@ fn run_case(runtime: &Runtime, tmpdir: &AbsolutePath, fixture_path: &Path) {
                 cmd.arg(step.as_str())
                     .env("PATH", &e2e_env_path)
                     .env("NO_COLOR", "1")
+                    .env("FORCE_COLOR", "0")
                     .current_dir(e2e_stage_path.join(&e2e.cwd));
                 let output = cmd.output().unwrap();