## 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",
    )
    breakdownBy: WebStatsBreakdown
    dateRange: Optional[DateRange] = None
    includeScrollDepth: Optional[bool] = None
    kind: Literal["WebStatsTableQuery"] = "WebStatsTableQuery"
    properties: List[Union[EventPropertyFilter, PersonPropertyFilter]]
    response: Optional[WebStatsTableQueryResponse] = None
    sampling: Optional[Sampling] = None
class WebTopClicksQuery(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    dateRange: Optional[DateRange] = None
    kind: Literal["WebTopClicksQuery"] = "WebTopClicksQuery"
    properties: List[Union[EventPropertyFilter, PersonPropertyFilter]]
    response: Optional[WebTopClicksQueryResponse] = None
    sampling: Optional[Sampling] = None
class AnyResponseType(
    RootModel[
        Union[
            Dict[str, Any], HogQLQueryResponse, HogQLMetadataResponse, Union[AnyResponseType1, Any], EventsQueryResponse
        ]
    ]
):
    root: Union[
        Dict[str, Any], HogQLQueryResponse, HogQLMetadataResponse, Union[AnyResponseType1, Any], EventsQueryResponse
    ]
class DashboardFilter(BaseModel):