## Is your feature request related to a problem?

It's currently not at all obvious that we apply a `LIMIT 100` clause to HogQL queries. This leads to confusion, like here: ZEN-9555.

## Describe the solution you'd like

We can probably get away with just some note somewhere.
Better yet, an "apply higher limit" button in the "reached end of results" message.

#### *Thank you* for your feature request – we love each and every one!

posthog/schema.py
model_config = ConfigDict(
        extra="forbid",
    )
    key: Literal["id"] = "id"
    label: Optional[str] = None
    type: Literal["cohort"] = "cohort"
    value: int
class CountPerActorMathType(str, Enum):
    avg_count_per_actor = "avg_count_per_actor"
    min_count_per_actor = "min_count_per_actor"
    max_count_per_actor = "max_count_per_actor"
    median_count_per_actor = "median_count_per_actor"
    p90_count_per_actor = "p90_count_per_actor"
    p95_count_per_actor = "p95_count_per_actor"
    p99_count_per_actor = "p99_count_per_actor"
class DatabaseSchemaQueryResponseField(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    chain: Optional[List[str]] = None
    fields: Optional[List[str]] = None
    key: str
    table: Optional[str] = None
    type: str
class DateRange(BaseModel):