## 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",
    )
    edge_limit: Optional[int] = None
    end_point: Optional[str] = None
    exclude_events: Optional[List[str]] = None
    funnel_filter: Optional[Dict[str, Any]] = None
    funnel_paths: Optional[FunnelPathType] = None
    include_event_types: Optional[List[PathType]] = None
    local_path_cleaning_filters: Optional[List[PathCleaningFilter]] = None
    max_edge_weight: Optional[int] = None
    min_edge_weight: Optional[int] = None
    path_groupings: Optional[List[str]] = None
    path_replacements: Optional[bool] = None
    path_type: Optional[PathType] = None
    paths_hogql_expression: Optional[str] = None
    start_point: Optional[str] = None
    step_limit: Optional[int] = None
class PropertyFilterType(str, Enum):
    meta = "meta"
    event = "event"
    person = "person"
    element = "element"
    feature = "feature"
    session = "session"
    cohort = "cohort"
    recording = "recording"
    group = "group"
    hogql = "hogql"
class PropertyMathType(str, Enum):