## 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",
    )
    complete: Optional[bool] = False
    end_time: Optional[AwareDatetime] = None
    error: Optional[bool] = False
    error_message: Optional[str] = ""
    expiration_time: Optional[AwareDatetime] = None
    id: str
    query_async: Optional[bool] = True
    results: Optional[Any] = None
    start_time: Optional[AwareDatetime] = None
    task_id: Optional[str] = None
    team_id: int
class QueryTiming(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    k: str = Field(..., description="Key. Shortened to 'k' to save on data.")
    t: float = Field(..., description="Time in seconds. Shortened to 't' to save on data.")
class RecordingDurationFilter(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    key: Literal["duration"] = "duration"
    label: Optional[str] = None
    operator: PropertyOperator
    type: Literal["recording"] = "recording"
    value: float
class Kind(str, Enum):