## 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",
    )
    events: List[EventType]
    recording_duration_s: Optional[float] = Field(default=None, description="Duration of the recording in seconds.")
    sessionId: Optional[str] = Field(default=None, description="Session ID. None means out-of-session events")
class TrendsFilter(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    aggregationAxisFormat: Optional[AggregationAxisFormat] = None
    aggregationAxisPostfix: Optional[str] = None
    aggregationAxisPrefix: Optional[str] = None
    breakdown_histogram_bin_count: Optional[float] = None
    compare: Optional[bool] = None
    decimalPlaces: Optional[float] = None
    display: Optional[ChartDisplayType] = None
    formula: Optional[str] = None
    hidden_legend_indexes: Optional[List[float]] = None
    showLabelsOnSeries: Optional[bool] = None
    showLegend: Optional[bool] = None
    showPercentStackView: Optional[bool] = None
    showValuesOnSeries: Optional[bool] = None
    smoothingIntervals: Optional[float] = None
class TrendsFilterLegacy(BaseModel):