Flaky e-remove test on Windows

[dsanders11]

I've seen this a couple of times now, on my local machine and on CI. A subsequent run passes.

$ nyc --reporter=lcov --reporter=text-summary jest --config=jest.fast.json
 FAIL  tests/e-remove-spec.js (24.473s)
  ● e-remove › removes the specified configuration from our list

    expect(received).toStrictEqual(expected) // deep equality

    Expected: 0
    Received: 1

      65 |       .name(configNameToRemove)
      66 |       .run();
    > 67 |     expect(result.exitCode).toStrictEqual(0);
         |                             ^
      68 |     expect(result.stdout.toLowerCase()).toEqual(expect.stringContaining('removed'));
      69 |   });
      70 | });

      at Object.<anonymous> (tests/e-remove-spec.js:67:29)

Test Suites: 1 failed, 1 of 3 total
Tests:       1 failed, 2 passed, 3 total
Snapshots:   0 total
Time:        25.714s
Ran all test suites.

=============================== Coverage summary ===============================
Statements   : 56.73% ( 316/557 )
Branches     : 46.75% ( 115/246 )
Functions    : 52.27% ( 46/88 )
Lines        : 58.17% ( 306/526 )
================================================================================

Might be some sort of race condition in the tests themselves.