## 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
) AS pdi
GROUP BY day_start, breakdown_value
"""
BREAKDOWN_ACTIVE_USER_INNER_SQL = """
SELECT counts as total, timestamp as day_start, breakdown_value
FROM (
    SELECT d.timestamp, COUNT(DISTINCT person_id) counts, breakdown_value FROM (
        SELECT toStartOfDay(toTimeZone(toDateTime(timestamp, 'UTC'), %(timezone)s)) as timestamp FROM events e WHERE team_id = %(team_id)s {parsed_date_from_prev_range} {parsed_date_to} GROUP BY timestamp
    ) d
    CROSS JOIN (
        SELECT toStartOfDay(toTimeZone(toDateTime(timestamp, 'UTC'), %(timezone)s)) as timestamp, {person_id_alias}.person_id AS person_id, {breakdown_value} as breakdown_value
        FROM events e
        {person_join}
        {groups_join}
        {sessions_join}
        {conditions}
        {null_person_filter}
        GROUP BY timestamp, person_id, breakdown_value
    ) e
    WHERE e.timestamp <= d.timestamp AND e.timestamp > d.timestamp - INTERVAL {prev_interval}
    GROUP BY d.timestamp, breakdown_value
    ORDER BY d.timestamp
) WHERE 11111 = 11111 {parsed_date_from} {parsed_date_to}
"""
BREAKDOWN_AGGREGATE_QUERY_SQL = """
SELECT {aggregate_operation} AS total, {breakdown_value} AS breakdown_value
FROM events e
{person_join}
{groups_join}
{sessions_join_condition}