fix(cdp): distinguish destination invocation statuses

[0xluffyb]

Problem

CDP destination invocation results need to remain unambiguous without relying on red and green. The existing status tags had text but no iconographic cue or explicit accessible name.

Changes

• Add a shared invocation status tag with distinct icons, visible text, and Status: … accessible labels
• Use the shared treatment in destination logs and testing results
• Cover success, failure, running, not-tested, and unknown states

How did you test this code?

I am an agent. I ran the focused Jest test, oxlint on all changed files, the frontend TypeScript check, and a Storybook browser check that asserted the visible icons and accessible labels. I also captured the destination logs in the normal palette and under a deuteranopia simulation.

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

Docs update

No docs update is needed because this changes the presentation and accessibility of existing statuses without changing product behavior.

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

Implemented with Capy. A shared component was chosen so logs and testing cannot drift in status semantics; icons are decorative to assistive technology while the tag carries the explicit accessible name. Verification used the existing multi-result destination Storybook fixture.

---

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