Drive cmd.Env from t.Setenv in endtoend tests

Mirror how the real CLI populates cmd.Env: t.Setenv every entry from
exec.json's Env map and then call opts.DebugFromEnv/ExperimentFromEnv.
This generalises to any env var a test wants to set (not just
SQLCDEBUG/SQLCEXPERIMENT) and keeps the test path closer to the
production code path.

https://claude.ai/code/session_01RCzB2JR5Y5ScFDUmwcxGVZ

Author: claude

internal/endtoend/endtoend_test.go

@@ -338,10 +338,13 @@ func TestReplay(t *testing.T) {
 				}
 
 				cfg := testctx.Config(t, path)
+				for k, v := range args.Env {
+					t.Setenv(k, v)
+				}
 				cmdOpts := cmd.Options{
 					Env: cmd.Env{
-						Debug:      opts.DebugFromString(args.Env["SQLCDEBUG"]),
-						Experiment: opts.ExperimentFromString(args.Env["SQLCEXPERIMENT"]),
+						Debug:      opts.DebugFromEnv(),
+						Experiment: opts.ExperimentFromEnv(),
 					},
 					Stderr: &stderr,
 				}