## 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
field_pageview = "$pageview"
    field_screen = "$screen"
    custom_event = "custom_event"
    hogql = "hogql"
class PathsFilter(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    edgeLimit: Optional[int] = None
    endPoint: Optional[str] = None
    excludeEvents: Optional[List[str]] = None
    funnelFilter: Optional[Dict[str, Any]] = None
    funnelPaths: Optional[FunnelPathType] = None
    includeEventTypes: Optional[List[PathType]] = None
    localPathCleaningFilters: Optional[List[PathCleaningFilter]] = None
    maxEdgeWeight: Optional[int] = None
    minEdgeWeight: Optional[int] = None
    pathDropoffKey: Optional[str] = None
    pathEndKey: Optional[str] = None
    pathGroupings: Optional[List[str]] = None
    pathReplacements: Optional[bool] = None
    pathStartKey: Optional[str] = None
    pathsHogQLExpression: Optional[str] = None
    startPoint: Optional[str] = None
    stepLimit: Optional[int] = None
class PathsFilterLegacy(BaseModel):