## 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/breakdown_props.py
filter: Filter,
    entity: Entity,
    aggregate_operation: str,
    team: Team,
    extra_params={},
    column_optimizer: Optional[ColumnOptimizer] = None,
    person_properties_mode: PersonPropertiesMode = PersonPropertiesMode.USING_PERSON_PROPERTIES_COLUMN,
    use_all_funnel_entities: bool = False,
):
    """
    Returns the top N breakdown prop values for event/person breakdown
    e.g. for Browser with limit 3 might return ['Chrome', 'Safari', 'Firefox', 'Other']
    When dealing with a histogram though, buckets are returned instead of values.
    """
    column_optimizer = column_optimizer or ColumnOptimizer(filter, team.id)
    date_params = {}
    query_date_range = QueryDateRange(filter=filter, team=team, should_round=False)
    parsed_date_from, date_from_params = query_date_range.date_from
    parsed_date_to, date_to_params = query_date_range.date_to
    date_params.update(date_from_params)
    date_params.update(date_to_params)