fix: align component example outputs with provider APIs

[Vukotije]

Fixes #3797

Summary

Example outputs shown in the workflow builder did not match what components actually emit, so users built expressions against the wrong shape. This PR updates integration and core component example JSON to match official provider/API documentation and the Emit() payloads in Go, then regenerates docs/components/*.mdx so docs stay in sync.

Changes are split one commit per integration (plus HTTP/Merge components and a final MDX regen commit) for easier review.

What changed

• ~95 example payload files under pkg/integrations/** and core components (http, merge)
• Regenerated docs/components/*.mdx via make gen.components.docs
• Corrected cases where examples were:
  • Over-trimmed (dropped valid API fields, including null values Statuspage and others return)
  • Empty or minimal data: {} while emit passes the full response body
  • Wrong field names or structure vs webhook/API docs (e.g. Merge sourceNodes vs sources, HTTP success payload including a spurious error field)
• Preserved existing placeholder conventions (timestamps, org/repo names) where the shape was already correct

Integrations touched

AWS, Bitbucket, CircleCI, Cloudflare, Dash0, Datadog, DigitalOcean, Discord, Docker Hub, Elastic, FireHydrant, GCP, GitHub, GitLab, Grafana, Hetzner, Honeycomb, LaunchDarkly, Logfire, New Relic, OpenAI, PagerDuty, Perplexity, Rootly, Semaphore, SendGrid, Slack, Microsoft Teams — plus HTTP and Merge core components.

Validation

• make check.example.payloads — envelope type matches each component’s Emit()
• make gen.components.docs — MDX regenerated from updated examples

Notes for reviewers

• Prefer reviewing per-integration commits rather than the full diff at once.
• Some integrations have two fix: commits (initial pass + restore of full API shapes); safe to squash per integration before merge if desired.
• make check.example.payloads checks type/envelope, not full provider fidelity — future work could add stricter guards against key loss vs baseline.

[superplanehq-integration]

👋 Commands for maintainers:

• /sp start - Start an ephemeral machine (takes ~30s)
• /sp stop - Stop a running machine (auto-executed on pr close)

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

There are 3 total unresolved issues (including 1 from previous review).

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

^{Reviewed by Cursor Bugbot for commit 6197fc4. Configure here.}