## 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",
    )
    hogql: Optional[str] = None
    is_cached: Optional[bool] = None
    last_refresh: Optional[str] = None
    next_allowed_client_refresh: Optional[str] = None
    results: List[WebOverviewItem]
    samplingRate: Optional[SamplingRate] = None
    timings: Optional[List[QueryTiming]] = None
class WebStatsBreakdown(str, Enum):
    Page = "Page"
    InitialPage = "InitialPage"
    InitialChannelType = "InitialChannelType"
    InitialReferringDomain = "InitialReferringDomain"
    InitialUTMSource = "InitialUTMSource"
    InitialUTMCampaign = "InitialUTMCampaign"
    InitialUTMMedium = "InitialUTMMedium"
    InitialUTMTerm = "InitialUTMTerm"
    InitialUTMContent = "InitialUTMContent"
    Browser = "Browser"
    OS = "OS"
    DeviceType = "DeviceType"
    Country = "Country"
    Region = "Region"
    City = "City"
class WebStatsTableQueryResponse(BaseModel):