## 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",
    )
    actions: Optional[List[Dict[str, Any]]] = None
    aggregation_group_type_index: Optional[float] = None
    breakdown: Optional[Union[str, float, List[Union[str, float]]]] = None
    breakdown_group_type_index: Optional[float] = None
    breakdown_hide_other_aggregation: Optional[bool] = None
    breakdown_normalize_url: Optional[bool] = None
    breakdown_type: Optional[BreakdownType] = None
    breakdowns: Optional[List[Breakdown]] = None
    date_from: Optional[str] = None
    date_to: Optional[str] = None
    entity_id: Optional[Union[str, float]] = None
    entity_math: Optional[str] = None
    entity_type: Optional[EntityType] = None
    events: Optional[List[Dict[str, Any]]] = None
    explicit_date: Optional[Union[bool, str]] = Field(
        default=None,
        description='Whether the `date_from` and `date_to` should be used verbatim. Disables rounding to the start and end of period. Strings are cast to bools, e.g. "true" -> true.',
    )
    filter_test_accounts: Optional[bool] = None
    from_dashboard: Optional[Union[bool, float]] = None
    insight: Optional[InsightType] = None
    interval: Optional[IntervalType] = None