[TS PBT] Run direct campaign controls from the existing CLI

[CaelmBleidd]

Expose the existing original-property campaign runner through usvm-ts-fast-check --mode PBT_ONLY|SYMBOLIC_ONLY|SEQUENTIAL --artifact <file.json>. One selected property and source root produce one UTF-16-safe PropertyCampaignArtifact snapshot, printed to stdout and saved to the requested file; the campaign is executed once.

The opt-in path reuses the existing seed, replay, explicit examples, run count, coverage options, total timeout and validation reserve. Exit code 1 preserves a confirmed violation even if later work reaches its deadline or fails; healthy completed controls return 0, and incomplete or unsupported outcomes return 2. A file write failure also returns 2 after retaining the actual result on stdout. Existing commands without --mode keep their previous execution path and output.

Stacked on #542 (caelmbleidd/pbt-campaign-artifact). Refs #354; this exposes the current direct controls and does not claim to complete the broader experiment task. The artifact schema is unchanged, and process/service loading and artifact persistence remain outside the runner's recorded campaign execution timing.

Validation:

• 41 focused Kotlin tests passed on Java 11 / Node 22: campaign CLI, legacy CLI, campaign runner and artifact tests; the final validation-only refactor was followed by another run of all 22 CLI tests.
• :usvm-ts-fast-check:installDist passed; the installed distribution ran all three modes in separate Java processes with exit 0, and stdout exactly matched each saved artifact.
• Strict detektMain and detektTest passed with zero code smells (ignoreFailures=false).

These are local checks; GitHub CI remains a separate check.