feat(webhooks): add event replay command

[gabrielmfern]

What

Adds resend webhooks events replay <webhookId> <eventId>, mirroring webhooks events get's argument parsing, prompts, and help text. Queues one more delivery of a webhook event — the same action as the dashboard's Replay button.

resend webhooks events replay 4dd369bc-aa82-4ff3-97de-514ae3000ee0 msg_1srOrx2ZWZBpBUvZwXKQmoEYga2

{"object":"webhook_event","id":"msg_1srOrx2ZWZBpBUvZwXKQmoEYga2"}

(response shape per the spec — no live call was made; see below)

Blocked on resend-node 6.26.0 publish

replay() ships in resend/resend-node#1087, open and not yet published to npm. package.json is bumped to resend@6.26.0 anyway to match convention, so:

• pnpm install --frozen-lockfile will fail in CI (404 fetching resend@6.26.0) until that version is published.
• The pnpm-lock.yaml integrity hash for resend@6.26.0 is computed from a local build of the resend-node PR branch, not the real npm tarball — it must be regenerated (pnpm install, unfrozen) once 6.26.0 actually publishes.
• Tested locally by linking against that local build instead: pnpm lint, pnpm typecheck, pnpm test (137 files, all passing), and pnpm build all pass against it.

Keeping this in draft until resend-node 6.26.0 is published, at which point the lockfile needs a refresh before merging.

resend/resend-node#1087, resend/resend-openapi#112, resend/resend-monorepo#9535

Part of DEV-2005.

Linear: https://linear.app/resend/issue/DEV-2017

[cubic-dev-ai]

All reported issues were addressed across 8 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>