fix: make std.text and std.date reachable as types via _self

[prql-bot]

Implements the _self option @kgutwin proposed in #6146, plus fixes for the two places _self leaked into user-facing messages.

std.prql declared type text = text / type date = date among the type primitives and then module text { … } / module date { … } under the same names. The module def came later and replaced the type decl, so both type lines were inert and std.text / std.date were unreachable as types. This moves each type alias inside its module as type _self, so the name carries both meanings:

$ prqlc compile 'let f = func x <std.text> -> x
from t
derive {y = f "a"}'
SELECT *, 'a' AS y FROM t

Bare <text> and text.lower are unaffected.

The _self leaks

@kgutwin flagged that the ambiguous-name hint became could be any of: std.date._self, this.date. There was a second leak too — a type mismatch against <std.text> reported expected type `_self` with Help: Type `_self` expands to `text` , where std.int (an ordinary type int = int alias) says expected type `int` .

Both come from _self being used as a display name, and both are fixed at the point of display:

• fold_type_def_stmt names a type _self after its containing module, so the type prints as text / date.
• ambiguous_error drops a trailing _self part from each candidate.

With those, test_ambiguous in error_messages.rs is unchanged — the hint is could be any of: std.date, this.date as before. No user-visible message changes in this PR.

Unblocking the duplicate check

The point of #6146 was that std.prql's reliance on module-over-type replacement blocks the non-module half of the duplicate check in fold_module_def_stmt. I verified locally that it's now unblocked: with a temporary check rejecting a module def over a non-module decl, the standard library loads clean and let x = 1 followed by module x { … } reports duplicate declarations of x instead of silently dropping x. That check isn't in this PR — it belongs on top of #6147.

Tests

Three inline tests in stmt.rs cover std.text as a type, the mismatch message under the module's own name, and the module still working as a function namespace. Remaining snapshot churn is byte-offset shifts in std.prql spans only.

Verification

cargo insta test -p prqlc -p prqlc-parser -p compile-files -p prqlc-macros -p mdbook-prql — all green (475 + 94 + 80 + 27 + 5 + 3 + 3 passed). cargo clippy -p prqlc --all-targets clean, cargo fmt --check clean.

The only snapshot diffs outside the new tests are span byte offsets in file 0 (std.prql), which shift on any edit to that file:

- span: 0:3522-3608
+ span: 0:3488-3574

cargo-insta isn't on the tend sandbox PATH (#6144), so I installed it with cargo install cargo-insta for this run.

[prql-bot]

Reviewed as the PR author's own reviewer, so this is a COMMENT rather than an approval.

The three guards are each scoped so they only fire for a module whose _self is a DeclKind::Ty, i.e. only for the two decls this PR adds — Module::lookup, wildcard resolution and expression resolution all behave exactly as before for this/that/table instances, whose _self stays an InstanceOf. <text> and <date> never reach any of this: type_expr's basic parser turns them into TyKind::Primitive before the ident branch is tried, so removing the two root-level type text = text / type date = date lines can only affect the std.-qualified path. test_ambiguous in error_messages.rs still pins could be any of: std.date, this.date, which is what guards the reverted _self stripping in ambiguous_error.

Two observations inline, neither blocking. One further follow-up, outside this diff: the changelog cites "an internal dump of the module" as the symptom, and that error is still what any other module produces in type position — <std.math> hits the same ok_or_else in fold_type with found: decl.to_string(), which renders Module { names: {...} } via the Display for DeclKind arm Self::Module(arg0) => f.debug_tuple("Module")…. Worth a separate PR to give that arm a short description; happy to push one if it's wanted.

[prql-bot]

Superseded by #6155, which fixed #6146 properly by moving the standard types into a dedicated std.types module rather than patching the collision with _self. Closing.