## 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
root: Union[TimeToSeeDataJSONNode, TimeToSeeDataWaterfallNode]
class TimeToSeeDataSessionsQuery(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    dateRange: Optional[DateRange] = Field(default=None, description="Date range for the query")
    kind: Literal["TimeToSeeDataSessionsQuery"] = "TimeToSeeDataSessionsQuery"
    response: Optional[TimeToSeeDataSessionsQueryResponse] = Field(default=None, description="Cached query response")
    teamId: Optional[int] = Field(default=None, description="Project to filter on. Defaults to current project")
class WebAnalyticsQueryBase(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    dateRange: Optional[DateRange] = None
    properties: List[Union[EventPropertyFilter, PersonPropertyFilter]]
    sampling: Optional[Sampling] = None
class WebOverviewQuery(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    dateRange: Optional[DateRange] = None
    kind: Literal["WebOverviewQuery"] = "WebOverviewQuery"
    properties: List[Union[EventPropertyFilter, PersonPropertyFilter]]
    response: Optional[WebOverviewQueryResponse] = None
    sampling: Optional[Sampling] = None
class WebStatsTableQuery(BaseModel):