## 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/test/test_trends.py
"breakdown": "order",
                        "actions": [{"id": action.pk, "type": "actions", "order": 0}],
                        "properties": [{"key": "name", "value": "person2", "type": "person"}],
                    }
                ),
                self.team,
            )
            event_response = Trends().run(
                Filter(
                    data={
                        "date_from": "-14d",
                        "breakdown": "order",
                        "events": [
                            {
                                "id": "watched movie",
                                "name": "watched movie",
                                "type": "events",
                                "order": 0,
                                "properties": [{"key": "name", "value": "person2", "type": "person"}],
                            }
                        ],
                    }
                ),
                self.team,
            )
        self.assertDictContainsSubset({"count": 2, "breakdown_value": "2"}, event_response[0])
        self.assertDictContainsSubset({"count": 1, "breakdown_value": "1"}, event_response[1])
        self.assertEntityResponseEqual(event_response, action_response)
    @test_with_materialized_columns(["$some_property"])
    def test_breakdown_filtering(self):