CLI: fix --skip-site-details argument for starting site which is already running

[nightnei]

Related issues

• Fixes STU-1272

Proposed Changes

If a site is already running and we execute node dist/cli/main.js site start --skip-log-details - the --skip-log-details argument is ignored.

Testing Instructions

1. Run node dist/cli/main.js site start --path=<PATH> --skip-log-details
2. Assert taht you don't see
   
3. Run again node dist/cli/main.js site start --path=<PATH> --skip-log-details
4. Assert taht you don't see (before if was anyway printed)
   

[wpmobilebot]

📊 Performance Test Results

Comparing 5146c07 vs trunk

site-editor

Metric	trunk	5146c07	Diff	Change
load	2840.00 ms	2835.00 ms	-5.00 ms	🟢 -0.2%

site-startup

Metric	trunk	5146c07	Diff	Change
siteCreation	7078.00 ms	7086.00 ms	+8.00 ms	🔴 0.1%
siteStartup	3927.00 ms	3927.00 ms	0.00 ms	⚪ 0.0%

---

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change

[sejas]

It works as expected and I don't see the login credentials when using the --skip-log-details parameter.

Before	After