## 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
auto = "auto"
    legacy_null_as_string = "legacy_null_as_string"
    legacy_null_as_null = "legacy_null_as_null"
    disabled = "disabled"
class PersonsArgMaxVersion(str, Enum):
    auto = "auto"
    v1 = "v1"
    v2 = "v2"
class PersonsOnEventsMode(str, Enum):
    disabled = "disabled"
    v1_enabled = "v1_enabled"
    v1_mixed = "v1_mixed"
    v2_enabled = "v2_enabled"
class HogQLQueryModifiers(BaseModel):
    model_config = ConfigDict(
        extra="forbid",
    )
    inCohortVia: Optional[InCohortVia] = None
    materializationMode: Optional[MaterializationMode] = None
    personsArgMaxVersion: Optional[PersonsArgMaxVersion] = None
    personsOnEventsMode: Optional[PersonsOnEventsMode] = None
class InsightFilterProperty(str, Enum):
    trendsFilter = "trendsFilter"
    funnelsFilter = "funnelsFilter"
    retentionFilter = "retentionFilter"
    pathsFilter = "pathsFilter"
    stickinessFilter = "stickinessFilter"
    lifecycleFilter = "lifecycleFilter"
class InsightNodeKind(str, Enum):