Frequent CLI intermittent test failure on Windows

[canova]

Noticed some intermittent CLI test failures. Here's an example: https://github.com/firefox-devtools/profiler/actions/runs/35850128777/job/107145574300

Summary of all failing tests
FAIL profiler-cli/src/test/integration/basic.test.ts (35.329 s)
  ● profiler-cli basic functionality › thread list prints a flat table

    Command failed with exit code 1

      161 |
      162 |   if (result.exitCode !== 0) {
    > 163 |     const error = new Error(`Command failed with exit code ${result.exitCode}`);
          |                   ^
      164 |     Object.assign(error, result);
      165 |     throw error;
      166 |   }

      at cli (profiler-cli/src/test/integration/utils.ts:163:19)
      at Object.<anonymous> (profiler-cli/src/test/integration/basic.test.ts:127:5)

Looks like a regression from #6273.

┆Issue is synchronized with this Jira Task

[canova]

This actually might not be a regression from #6273. It might be more of an issue with how the CLI integration tests are set up.