## 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
if response["breakdown_value"] == "person2":
                self.assertEqual(response["count"], 3)
            if response["breakdown_value"] == "person3":
                self.assertEqual(response["count"], 3)
    def test_breakdown_by_property_pie(self):
        with freeze_time("2020-01-01T12:00:00Z"):  # 
            person1 = _create_person(team_id=self.team.pk, distinct_ids=["person1"], immediate=True)
            person2 = _create_person(team_id=self.team.pk, distinct_ids=["person2"], immediate=True)
            person3 = _create_person(team_id=self.team.pk, distinct_ids=["person3"], immediate=True)
        _create_event(
            team=self.team,
            event="watched movie",
            distinct_id="person1",
            timestamp="2020-01-01T12:00:00Z",
            properties={"fake_prop": "value_1"},
        )
        _create_event(
            team=self.team,
            event="watched movie",
            distinct_id="person2",
            timestamp="2020-01-01T12:00:00Z",
            properties={"fake_prop": "value_1"},
        )
        _create_event(
            team=self.team,
            event="watched movie",
            distinct_id="person2",
            timestamp="2020-01-01T12:00:00Z",
            properties={"fake_prop": "value_1"},
        )