Fix: Always disable Jest globalSetup/globalTeardown for Codeflash tests

[mohammedahmed18]

Problem

When test files were inside the project root (the most common case), Codeflash did NOT create the runtime config that disables globalSetup/globalTeardown. This caused Jest to use the project's original config WITH globalSetup intact, leading to systematic failures when globalSetup required unavailable infrastructure:

Error: Jest: Got error running globalSetup - /workspace/target/globalSetup.ts,
reason: Command failed: docker context ls --format json
/bin/sh: 1: docker: not found

Root Cause

In test_runner.py, the runtime config was only created when tests were outside the project root:

if any(not Path(d).is_relative_to(resolved_root) for d in test_dirs):
    jest_config = _create_runtime_jest_config(...)

The runtime config serves two purposes:

1. Adding test directories to Jest's roots (for tests outside project root)
2. Disabling globalSetup/globalTeardown (needed ALWAYS)

The condition checked for (1) but ignored that (2) is needed in ALL cases.

Solution

Always create runtime config when jest_config and test_files exist, regardless of test location:

if test_files and jest_config:
    test_dirs = {str(Path(f).resolve().parent) for f in test_files}
    jest_config = _create_runtime_jest_config(jest_config, effective_cwd, test_dirs)

Impact

• Affected: ALL projects with globalSetup/globalTeardown in Jest config
• Reproducibility: 100% systematic
• Example trace: 04dc4dcf-ca9f-449e-aed5-7a82f28c5e23
• Symptom: "Couldn't run any tests for original function" (all optimizations skip)

Changes

• test_runner.py: Updated 3 functions:
  • run_jest_behavioral_tests
  • run_jest_benchmarking_tests
  • run_jest_line_profiling_tests
• New test file: test_globalsetup_invocation_bug.py (3 test cases)
• All existing tests still pass (9/9 globalSetup-related tests pass)

Testing

• ✅ 3 new unit tests verify fix
• ✅ 6 existing globalSetup tests still pass
• ✅ Manual verification: rerun of trace 04dc4dcf-ca9f-449e-aed5-7a82f28c5e23 now succeeds
• ✅ No "docker: not found" errors in test runs

Fixes #18