fix(ci): upgrade PostHog CLI for release races

[jonathanlab]

Summary

• upgrade the root @posthog/cli dependency from 0.7.5 to 0.8.4
• use the upstream concurrent release creation fix shipped in CLI 0.8.2
• remove the need for workflow-level build retries

Why

Parallel release jobs can both resolve the same sourcemap release as absent, then race to create it. The losing process receives release_hash_in_use, which CLI 0.7.5 treats as fatal. CLI 0.8.2 added explicit handling for this exact race: it recognizes the structured conflict and resolves the release created by the winning process.

The Rollup plugin resolves posthog-cli from the repository-level node_modules/.bin, so the root dependency controls the binary used in release builds.

Upstream fix: PostHog/posthog#70061

Validation

• pnpm install
• node_modules/.bin/posthog-cli --version → posthog-cli 0.8.4
• inspected the upstream fix and confirmed it handles structured release_hash_in_use conflicts

[trunk-io]

😎 Merged successfully - details.

[greptile-apps]

Prompt To Fix All With AI

### Issue 1
scripts/build-electron-vite-with-retry.mjs:35-40
**Retry flow lacks automated coverage**

All platform release builds now depend on branches for successful retries, exhausted retries, and immediate non-retryable failures, but these paths have only manual simulation coverage. Add parameterized automated tests so changes to error matching, attempt limits, or exit-code propagation do not silently break releases.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "fix(ci): retry sourcemap release creatio..." | Re-trigger Greptile}