CLI: Implement studio site set-php-version

[fredrikekelund]

Related issues

• Fixes STU-953

Proposed Changes

• Added a studio site set-php-version command, which updates the appdata file and restarts the site if running.

Testing Instructions

1. Run npm run cli:build
2. Run node dist/cli/main.js site set-php-version true --path PATH_TO_SITE (where PATH_TO_SITE is the path to a Studio site)
3. Ensure that it succeeds
4. Run node dist/cli/main.js site start --path PATH_TO_SITE
5. Run node dist/cli/main.js site set-php-version 8.2 --path PATH_TO_SITE
6. Ensure that the site restarts successfully (assuming the site wasn't already running PHP 8.2, in which case it will return an error)

Pre-merge Checklist

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

[github-actions]

📊 Performance Test Results

Comparing 67a338e vs trunk

site-editor

Metric	trunk	67a338e	Diff	Change
load	8687.00 ms	8858.00 ms	+171.00 ms	🔴 2.0%

site-startup

Metric	trunk	67a338e	Diff	Change
siteCreation	15174.00 ms	13345.00 ms	-1829.00 ms	🟢 -12.1%
siteStartup	5014.00 ms	5954.00 ms	+940.00 ms	🔴 18.7%

---

Results are median values from multiple test runs.

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

[bcotrim]

Code LGTM and works as described.

While reviewing, I wondered if we should have a studio site update command instead of separate set-* commands.

Advantages:

1. Consistent with studio create - Same option names (--php, --domain, --https)
2. Batch updates - One command, one restart instead of potentially 3
3. Less code - Shared boilerplate (load site → lock appdata → update → restart if running)

What do you think?

[fredrikekelund]

While reviewing, I wondered if we should have a studio site update command instead of separate set-* commands.

I like that idea 👍 I have a whole train of PRs waiting to merge here, though (#2151, this, and #2155). I'd prefer to land all three and then circle back to refactor the set-* commands into a single one.