fix: have tap run acknowledge a running spec instead of dumping it

[estrada9166]

• Closes https://cypress-io.atlassian.net/browse/AW-42

Additional details

---

Note

Low Risk
Scoped TAP CLI UX and JSON shape change for tap run; no server or test-runner behavior changes, though --json consumers must expect the new fields.

Overview
cypress tap run no longer prints or returns testing type and browser as if the run were fully launched. It now treats the command as an immediate acknowledgement that the spec was requested, with progress meant to come from cypress tap status.

The TapRunResult shape and --json output drop testingType and browser in favor of status: 'running' plus the spec path. Human output switches from a launch summary (▶ spec + definition list) to ● {spec} is running and a muted hint to use tap status. Comments, unit tests, system-test snapshots, and the changelog are updated to match.

^{Reviewed by Cursor Bugbot for commit b21c30e. Bugbot is set up for automated code reviews on this repo. Configure here.}

Steps to test

How has the user experience changed?

PR Tasks

• Is there an associated issue with maintainer approval for PR submission?
• Have tests been added/updated?
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2065cf6. Configure here.}

New commits pushed (auto-approval was for 2065cf6, head is now c7980fe). Auto-approval dismissed pending Cursor Bugbot re-review of the new head SHA.