feat(cli): point telemetry at the EU PostHog project
Points the CLI telemetry at the EU PostHog project through t.chainloop.dev, and fixes two problems in the events themselves.
Telemetry destination
The endpoint and key now target the EU project. Both stay in-source defaults so builds outside the release pipeline (Homebrew, go install) keep reporting, and GoReleaser consumes POSTHOG_API_KEY / POSTHOG_ENDPOINT when they are set, falling back to those defaults otherwise. The release workflow already exported both secrets but nothing read them, so the endpoint was effectively a constant; it is now a release-time input.
The endpoint is compiled in and has no runtime override, so binaries released before this change keep reporting to crb.chainloop.dev. That host stays frozen on the previous project rather than being repointed, and the sandbox egress allowlist keeps both hosts so older tags still work in a sandbox.
Group assignment
Setting the organization group replaced the groups map instead of adding to it, so cp_installation was dropped from every event that carried an organization. Since only API tokens carry an org id, this split all traffic in two: API-token events had organization alone, everything else had cp_installation alone, and no event ever carried both. Installation-level aggregation therefore never saw CI traffic, and installations used exclusively from CI with an API token were absent from it entirely.
Both groups now travel together on a single event. The underlying values were always present as event properties, so this restores the group dimension rather than recovering lost data, and it does not backfill history.
organization remains API-token-only, because user and federated tokens do not carry an org id at that point in the command lifecycle. This makes the index assignment stable and both groups present when known; giving user-token events an organization group needs the org UUID on the telemetry path and is left as a follow-up.
Alias volume
An alias between the machine and the account was enqueued on every authenticated command, making $create_alias roughly a third of the project's total event volume. It is now limited to interactive user sessions outside CI, which is the only case where stitching a pre-login machine identity onto an account is meaningful. API tokens belong to an organization rather than a person, and federated tokens resolve to the issuer URL, which is identical across installations, so aliasing those merged unrelated CI runners into a single person.
Refs PFM-7213.
AI assistance: this change was produced with Claude Code. Affected commits carry an Assisted-by: trailer, per AI_POLICY.md.