feat(slack): add author, space, and environment context to notifications [AIS-323]

[Mitch Goudy (mgoudy91)]

What

Enriches the Contentful → Slack notification payload with the entry author, space name, and environment ID, so notifications carry the context requested in #10075.

• Header now reads e.g. An entry was published by Jane Doe in space "Marketing" (master environment)!
• Context line lists content type, date, author, space, and environment.

Why

Customer feature request (#10075, ZoomInfo). The current notification only shows the entry name, content type, and date, which isn't enough context to act on in a shared channel.

How

Based on the prototype service.ts / types.ts attached to the issue by Russell Schwager (@rschwager). Two new CMA lookups are added inside getResolvedEntity:

• user.getManyForSpace → resolves the actor's display name (falls back to email, then user ID)
• space.get → resolves the space name (falls back to space ID)

Both are wrapped in try/catch with ID fallbacks, so a failed lookup degrades gracefully rather than dropping the notification. Environment ID comes straight off the event body (no extra call).

Tests

• Extended the getResolvedEntity unit tests to assert the new actorName, spaceName, and environmentId fields across all four event types, and stubbed the new user / space CMA calls in the mock client.
• Full suite green (56 passing), tsc --noEmit clean, ESLint + Prettier clean on the changed files.

Notes for reviewers

• Opened as draft: this came in off-roadmap from a customer prototype. Flagging for the team to decide whether to prioritize/merge rather than committing to ship.
• Two additional CMA calls per notification (user list + space get). Worth a look if we're concerned about added latency or rate-limit pressure on high-volume spaces — could be cached or made opt-in if needed.

Closes #10075

🤖 Generated with Claude Code