## Bug description

When calculating Trends results with an aggregated (e.g. single output, like big number) display type, WAU/MAU don't work. This is because we have an `ACTIVE_USERS_SQL` query for time series display types, but we don't have a version of this for aggregated display types. (See ZEN-1043.)

## How to reproduce

1. Create an insight with a single WAU or MAU series.
2. Switch display type to "Number".
3. Open the "Debug ClickHouse queries" modal from the command palette.
4. See `COUNT(*)` instead of `COUNT(DISTINCT person_id)`.

#### *Thank you* for your bug report – we love squashing them!

posthog/queries/trends/sql.py
{actions_query}
"""
BREAKDOWN_COHORT_JOIN_SQL = """
INNER JOIN (
    {cohort_queries}
) ep
ON e.distinct_id = ep.distinct_id where team_id = %(team_id)s {event_filter} {filters} {parsed_date_from} {parsed_date_to} {actions_query} {null_person_filter}
"""
_LIFECYCLE_EVENTS_QUERY = """
SELECT
    person_id,
    /*
        We want to put the status of each period onto it's own line, so we
        can easily aggregate over them. With the inner query we end up with a structure like:
        person_id  |  period_of_activity  | status_of_activity  | dormant_status_of_period_after_activity
        However, we want to have something of the format:
        person_id  | period_of_activity          |  status_of_activity
        person_id  | period_just_after_activity  |  dormant_status_of_period_after_activity
        such that we can simply aggregate over person_id, period.
    */
    arrayJoin(
        arrayZip(
            [period, period + INTERVAL 1 {interval_expr}],
            [initial_status, if(next_is_active, '', 'dormant')]
        )
    ) AS period_status_pairs,
    period_status_pairs.1 as start_of_period,
    period_status_pairs.2 as status
FROM (
    SELECT