## 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
SessionsTimelineQuery,
            HogQLQuery,
            HogQLMetadata,
            WebOverviewQuery,
            WebStatsTableQuery,
            WebTopClicksQuery,
        ]
    ] = Field(default=None, description='Query within which "expr" is validated. Defaults to "select * from events"')
    filters: Optional[HogQLFilters] = None
    kind: Literal["HogQLMetadata"] = "HogQLMetadata"
    response: Optional[HogQLMetadataResponse] = Field(default=None, description="Cached query response")
    select: Optional[str] = Field(
        default=None, description="Full select query to validate (use `select` or `expr`, but not both)"
    )
    table: Optional[str] = Field(default=None, description="Table to validate the expression against")
class QueryRequest(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    async_: Optional[bool] = Field(
        default=None,
        alias="async",
        description="(Experimental) Whether to run the query asynchronously. Defaults to False. If True, the `id` of the query can be used to check the status and to cancel it.",
        examples=[True],
    )
    client_query_id: Optional[str] = Field(
        default=None, description="Client provided query ID. Can be used to retrieve the status or cancel the query."
    )
    query: Union[
        EventsNode,