Remove dead process.env.CI skip guards from the integration tests

[pubino]

Follow-up to #29, which flagged these.

All four integration suites opened with a guard intended to skip them in CI:

if (process.env.CI) {
  console.log('Skipping ... in CI environment');
  return;
}

The guards never fired. The suites run via docker compose run, and the test service in docker-compose.yml passes only its explicit environment: list, so CI never reaches the container — process.env.CI is undefined inside it even on a GitHub runner. These tests have always run in CI, which is exactly what the guards were written to prevent.

Why remove rather than propagate CI

These four files are the entire integration suite, so honouring the guards would leave CI with no integration coverage.

One correction to what I wrote in #29: I said honouring them would "green CI while testing nothing." That's not right — Jest rejects a describe block containing no tests, so with CI set all four suites error out. Demonstrated in the container:

	Test Suites	Tests
guards present, CI=true	4 failed, 4 total	0 total
guards removed, CI=true	4 passed, 4 total	40 passed

So the guards would have failed loudly rather than quietly — smaller risk than I first described, but either way they no longer describe intended behaviour and are misleading to read.

The flaky-browser-launch concern behind them is better addressed at the source: the unbounded PlaywrightManager.close() that was hanging the keepalive hooks got fixed in b8c907a.

Verification

In the test container:

• CI=true npm run test:integration:direct — 40/40 pass (was 0 tests / 4 failed suites with the guards)
• npm run test:all — 136/136 pass, 10/10 suites

No production code touched; the diff is 24 deleted lines across the four test files.