[WIP]: Wire selective sync execution to pull-files/pull-db

[epeicher]

Related issues

• Related to STU-1816

How AI was used in this PR

AI (Claude Code) implemented this draft, guessing the forthcoming pull-files/pull-db Reprint command interface (names, arguments, and which command owns flatten/runtime are marked TODO(reprint pull-files/pull-db)). Reviewers should focus on whether the command split and arguments match Reprint's planned design rather than on polish.

Proposed Changes

⚠️ Draft / proof of concept. Stacked on #3976 (review/merge that first); depends on a reprint.phar that ships the new high-level pull-files/pull-db commands (not released yet), so it does not run end-to-end today.

Makes the selective-sync menu actually selective by wiring the captured choice to execution:

• Pulls only the wp-content folders the user picked (--only).
• Skips the database entirely when the user excludes it (the pull-db step is not called), leaving the local database untouched on a re-pull.

The site-clone pipeline is decomposed into three high-level commands — pull-files (files + flattened layout) → conditional pull-db (database) → apply-runtime (server config, last) — instead of the single composite pull. This keeps Studio simple and host-agnostic: it just chooses files vs database and passes --only; the new commands own the internal complexity.

Testing Instructions

• Unit tests assert the command sequence (pull-files always, pull-db only when the database is selected, --only on pull-files): npm test -- apps/cli/commands/tests/pull-reprint.test.ts.
• End-to-end testing requires a reprint.phar that implements pull-files/pull-db.

Pre-merge Checklist

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