## 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/breakdown.py
from posthog.queries.session_query import SessionQuery
from posthog.queries.trends.sql import (
    BREAKDOWN_ACTIVE_USER_CONDITIONS_SQL,
    BREAKDOWN_ACTIVE_USER_INNER_SQL,
    BREAKDOWN_AGGREGATE_QUERY_SQL,
    BREAKDOWN_COHORT_JOIN_SQL,
    BREAKDOWN_CUMULATIVE_INNER_SQL,
    BREAKDOWN_HISTOGRAM_PROP_JOIN_SQL,
    BREAKDOWN_INNER_SQL,
    BREAKDOWN_PROP_JOIN_SQL,
    BREAKDOWN_QUERY_SQL,
    SESSION_DURATION_BREAKDOWN_AGGREGATE_QUERY_SQL,
    SESSION_DURATION_BREAKDOWN_INNER_SQL,
    VOLUME_PER_ACTOR_BREAKDOWN_AGGREGATE_SQL,
    VOLUME_PER_ACTOR_BREAKDOWN_INNER_SQL,
)
from posthog.queries.trends.util import (
    COUNT_PER_ACTOR_MATH_FUNCTIONS,
    PROPERTY_MATH_FUNCTIONS,
    ensure_value_is_json_serializable,
    enumerate_time_range,
    get_active_user_params,
    parse_response,
    process_math,
)
from posthog.queries.util import start_of_week_fix
from posthog.utils import encode_get_request_params
class TrendsBreakdown:
    DISTINCT_ID_TABLE_ALIAS = "pdi"
    def __init__(