fix(cli): stop error tracking for missing bundle versions

[posthog-eu]

Summary

• A missing bundle version is a user typo or a version that was never uploaded, not a CLI crash — but the team pays for it in triage, because every failure opens a fresh error tracking issue.
• getVersionData in cli/src/api/versions.ts threw a plain Error when the named bundle was not in the active list. isExpectedUserError only knew about bad API keys and not-yet-created apps, so this failure reached error tracking as an unhandled crash.
• The message interpolated the app id and the version, so each distinct version string got its own fingerprint — one problem split into dozens of single-event issues.
• This is the shared chokepoint for channel set, bundle delete, and bundle cleanup.

Fix — the same pattern PR #2885 and PR #2934 applied to auth failures and upload aborts:

Before	After
throw new Error(\App version ${appid}@${bundle} doesn't exist`)`	throw new CliUserError('App version doesn\'t exist', { appId, version })

• CliUserError is skipped by shouldCapturePosthogException via instanceof, so error tracking no longer opens an issue.
• The non-zero exit, the printed message, and the trackCommandFailed analytics stay unchanged.
• The app id and version move into the CliUserError context object, so the message is now constant and one problem stays one issue.
• The two sibling throws in deleteAppVersion get the same treatment.

Test plan

• cd cli && bun run lint — passes clean on the changed file.
• Manual: run capgo channel set <channel> --bundle <version> with a version that was never uploaded. The CLI still prints App version <app>@<version> doesn't exist and exits non-zero, but no error tracking $exception issue is opened.

Screenshots

Checklist

• My code follows the code style of this project and passes
  bun run lint:backend && bun run lint.
• My change requires a change to the documentation.
• I have updated the documentation
  accordingly.
• My change has adequate E2E test coverage.
• I have tested my code manually, and I have provided steps how to reproduce
  my tests

---

Created with PostHog Desktop from this inbox report.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[codspeed-hq]

Merging this PR will not alter performance

✅ 43 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing posthog-self-driving/fixcli-stop-error-reporting-missing-bae501 (fa5a7d0) with main (e745fdd)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud