Sentry issue state that respects environment so ignore in dev does not suppress prod alerts

Sentry's ignore and resolve workflow actions apply globally across all environments. When an engineer mutes a noisy issue in staging or dev, that same mute silences the issue in production too. Teams working across multiple environments constantly hit false quiet in prod or get buried in dev noise they cannot selectively suppress. This service sits as a thin webhook and API layer over Sentry: it intercepts Sentry webhooks, maintains its own per-project per-environment ignore/resolve state in a lightweight database, and gates alert forwarding based on that state. Engineers interact through a small dashboard or Slack slash command to set environment-scoped mutes with optional TTLs. The service re-opens alerts that arrive from environments where the issue is not muted, even if Sentry itself has globally ignored it. It requires no changes to how Sentry is configured beyond adding a webhook endpoint.