## 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",
    )
    kind: Literal["TimeToSeeDataQuery"] = "TimeToSeeDataQuery"
    response: Optional[Dict[str, Any]] = Field(default=None, description="Cached query response")
    sessionEnd: Optional[str] = None
    sessionId: Optional[str] = Field(default=None, description="Project to filter on. Defaults to current session")
    sessionStart: Optional[str] = Field(
        default=None, description="Session start time. Defaults to current time - 2 hours"
    )
    teamId: Optional[int] = Field(default=None, description="Project to filter on. Defaults to current project")
class TimeToSeeDataSessionsQueryResponse(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    results: List[Dict[str, Any]]
class TimeToSeeDataWaterfallNode(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    kind: Literal["TimeToSeeDataSessionsWaterfallNode"] = "TimeToSeeDataSessionsWaterfallNode"
    source: TimeToSeeDataQuery
class TimelineEntry(BaseModel):