What an application's steps were given and what they used, across
the runs that ran it, by version (and variant): distinct runs and steps, the cpu
and memory the steps were given most often, and the median, 95th
percentile and maximum of each step's peak memory, peak cpu (from
the node's Container Insights, or a Lambda step's REPORT line),
duration (succeeded steps) and cost. One sample per step is kept
when a run turns terminal; the newest 1000 are aggregated. Access
is as the application's counters: a workspace member with
organization_id, otherwise a public application or its owner.