fix(queries): compile decorator queries: and match ngtsc's query options

[ashley-hunter]

Stack (3/5): #493 inputs/outputs → #494 transform validation → #495 queries: → #496 .d.ts transform types → #504 signal API import identity. This is #495.

Compiles queries: declared in @Directive / @Component metadata, and matches ngtsc on a few member-query options.

The bug

@Directive({ selector: '[d]', queries: { el: new ViewChild('el') } })
export class D { el!: ElementRef; }

compiled with no view query, so el was never set. The queries key was ignored like inputs: was.

The fix

queries: is parsed like ngtsc's extractQueriesFromDecorator: new ViewChild/ViewChildren/ContentChild/ContentChildren(...) imported from @angular/core (directly or through a namespace import), appended after the member queries. It raises ngtsc's diagnostics word for word:

• not an object literal
• not a query type
• missing or extra arguments
• non-object options
• a non-boolean descendants, static or emitDistinctChangesOnly
• predicates that can't be interpreted
• a signal query for the same property (only Angular's own viewChild/contentChild..., imported from @angular/core directly, with an alias or through a namespace)

An option or predicate element imported from another file ({descendants: FLAG}, new ViewChild([...SELS])) gets the same message as in #493 (... depends on 'FLAG', which is imported from another module. OXC compiles one file at a time ...) instead of ngtsc's wrong-type error for a value oxc never read.

Member query decorators now also match ngtsc:

• @ViewChild/@ViewChildren honour descendants and emitDistinctChangesOnly. They were hard-coded before, so this changes the emitted query flags for code that sets them.
• A predicate referencing a same-file string const (@ViewChild(SELECTOR)) compiles to that selector instead of a type predicate.
• forwardRef(function () { return X; }), and forwardRef behind parentheses or as, is unwrapped like the arrow form. ns.forwardRef(...) is only unwrapped when ns is a namespace import of @angular/core; util.forwardRef(() => X) is kept as the predicate. A bare forwardRef is unwrapped only when it's imported from @angular/core (aliases too), like ngtsc; the public extract_view_queries / extract_content_queries, which don't get the file's imports, still match it by name.

extract_class_queries returns a class's queries as they're compiled. The compiler and the NAPI extractComponentMetadataSync both use it, so the metadata API now reports the same queries.

Member decorators through a namespace (@core.Input(), @core.ViewChild(), ...) are now matched using the file's imports, passed in through StringConsts (extract_input_metadata_in, extract_output_metadata_in, and the query and host variants), instead of state set by the compiler. The compiler and extractComponentMetadataSync both use them, so the NAPI metadata now includes @core.Input() too, and still ignores a namespace that isn't @angular/core.

Member query decorators read their options through the same code as queries:, like ngtsc's extractDecoratorQueryMetadata: const flags, parentheses and as are read, and wrong-type or non-object options, uninterpretable predicates and wrong argument counts report ngtsc's errors. This also changes emitted flags for code that passes const options. The error check reads queries: with the source text, so a function-expression predicate no longer gets a false "cannot be interpreted" error.

Tests

Added to the ngtsc snapshot: Angular's queries specs (ngtsc_spec's decorator-queries errors and "should generate queries for components/directives", forwardRef, and the authoring_queries_spec collisions), plus probes of every error, the flags, the ordering and forwardRef through local, @angular/core and other namespaces. One probe is skipped: ngtsc also reports its separate check for signal query functions called outside a member initializer, which oxc doesn't implement. A separate test covers the imported-value messages. A new NAPI test covers extractComponentMetadataSync: queries (this failed before the fix), and namespaced member decorators through @angular/core versus another module.