Track workspace activity: suspend a workspace

Problem to solve

We have instrumentation that can tell us how many workspaces have been created. But how many of these workspaces are created, then paused/suspended, then resumed? How many go through that cycle multiple times before being terminated? Understanding how often this operation is used and comparing that with customer input, we can determine whether we need to support additional workflows around suspending and resuming workspaces, or if we need to change our assumptions about how long workspaces need to stay around.

Proposal

Track an event for a workspace that's suspended/paused, then an event for a workspace that's resumed.

In a perfect world, we'd be able to determine with this data how many workspaces are paused and never resumed.