CLI test: add HTTP response check for created site

[gavande1]

Related issues

• Related to STU-1867

How AI was used in this PR

Claude was used to write the code and explore the solution. The author reviewed it manually.

Proposed Changes

Follow-up to the CLI e2e tests in #3947. The site create test only asserted persisted state on disk. This adds a real check: after creating and starting a site, the test requests its homepage and confirms a 200 with HTML, so it now fails if a created site cannot be served.

This does not cover the custom-domain and HTTPS case, which cannot run in an isolated, headless test. See the discussion in #3947.

Testing Instructions

1. Build the CLI with npm run cli:build.
2. Run npm test -- apps/cli/commands/site/tests/create.e2e.test.ts --tagsFilter='e2e' and confirm both tests pass.
3. Run the same with --tagsFilter='!e2e' and confirm the tests are skipped, so the fast suite is unaffected.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[wpmobilebot]

📊 Performance Test Results

Comparing a5108d1 vs trunk

app-size

Metric	trunk	a5108d1	Diff	Change
App Size (Mac)	1411.92 MB	1411.92 MB	+0.00 MB	⚪ 0.0%

site-editor

Metric	trunk	a5108d1	Diff	Change
load	1104 ms	1091 ms	13 ms	⚪ 0.0%

site-startup

Metric	trunk	a5108d1	Diff	Change
siteCreation	6477 ms	6471 ms	6 ms	⚪ 0.0%
siteStartup	2389 ms	2392 ms	+3 ms	⚪ 0.0%

---

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)

[gcsecsey]

Thanks for adding the HTTP checks @gavande1! 🙌

The new tests are working well:

And they're skipped when filtered out as expected:

I added a note about the PHP binary being available on CI.