Support escalation button non-prod behavior

[mehansen]

Background

On the support admin dashboard, we have an "Escalate to engineering" task that allows support to send a Slack message to our #proj-sr-support-notifications channel, letting the on-call person know a new request has been added to our escalation tracker.

In non-prod environments, clicking this button results in an error.

It would be nice if we had a non-prod behavior that handled this in a way more similar to production. For someone unfamiliar with the implementation of the button the current behavior might lead them to believe something is broken. Something that gives a success toast if we hit the backend with the right mutation would also allow us to test frontend changes to this page in a lower environment.

This is probably low priority, since this page is only visible to support admins and interacting with the page doesn't impact users directly.

Acceptance Criteria

When I click the support escalation button in a non-prod environment, I do not get an error, provided we've hit the backend with the correct mutation. Alternately, when I click the support escalation button in a non-prod environment, we receive a test message in the #proj-sr-support-notifications or another channel.

Additional context

Open questions:

• do we need to have a DemoSlackService or is that overkill? and is it enough to just handle it in the frontend and log something