HogQL parser rejects an alias binding followed by an operator

Bug description

The parser accepts expr AS alias and it accepts (expr AS alias) <op> …, but it rejects
expr AS alias <op> … without the parentheses. The alias binds, and then the operator is
treated as a trailing token rather than as an operator applied to the aliased expression.

The failure is a parse error, so it lands before any resolution or type checking.

How to reproduce

Run against master:

from posthog.hogql.parser import parse_select

parse_select("SELECT 1 AS x > 0")

Result:

SyntaxError: trailing tokens after expression: '>' (Gt)

The same shape fails with every operator class tried:

The last two matter most: inside a function call there is no trailing-token position at all,
so the parse fails on the argument list.

Expected

An alias binding should be able to participate in a surrounding expression without
parentheses, as it can in ClickHouse SQL.

Notes

Executed against master today, not inferred. The relevant precedence handling is in
rust/hogql/parser/src/parse/expr.rs (after_bare_alias); the grammar has no
corresponding alias-then-operator production.

Worth confirming the exact ClickHouse-side acceptance boundary before fixing, so the
two parsers are brought into line deliberately rather than by guess.

Start in rust/hogql/parser/src/parse/expr.rs, especially after_bare_alias, and reproduce the listed queries through posthog.hogql.parser.parse_select. Confirm the exact ClickHouse acceptance boundary, then bring the grammar and precedence handling into line so alias bindings work with surrounding operators without parentheses, including function arguments.