fix(component): pool content-query predicates before view-query predicates

Upstream ngtsc's `compileComponent` emits the `contentQueries:` field
before `viewQuery:` in the component definition object literal, and
pools predicates in that order. The resulting `_c<N>` constant-table
indices end up content-first (`_c0`, `_c1` for content; `_c2`, `_c3`
for view) — the form pinned by every compliance golden under
`compiler-cli/test/compliance/test_cases/signal_queries/`.

This compiler had the order reversed (view queries pooled first), so
the same source produced `_c0`/`_c1` for view queries and `_c2`/`_c3`
for content — runtime-equivalent but breaks emit-anchored tooling and
diff-based comparisons against Angular's own goldens.

Fix: swap the call order in `compile_component` so content queries
are pooled and emitted before view queries. No behavioral change at
runtime — the metadata field order is unchanged in the output object
literal (Angular's runtime reads both fields by name); only the
const-table indices shift back into upstream alignment.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: brandonroberts

crates/oxc_angular_compiler/src/component/transform.rs

@@ -3420,28 +3420,34 @@ fn compile_component_full<'a>(
     // See: packages/compiler/src/render3/view/compiler.ts lines 192-212
     let attrs_ref = pool_selector_attrs(allocator, &mut job, metadata);
 
-    // BEFORE template compilation: Pool view query predicates.
-    // TypeScript Angular pools query predicates BEFORE template compilation and pure functions.
-    // This ensures correct constant ordering: attrs -> query predicates -> pure functions.
-    let view_query_fn = if !view_queries.is_empty() {
+    // BEFORE template compilation: Pool query predicates so they
+    // appear in the constant table as `attrs -> query predicates ->
+    // pure functions`.
+    //
+    // Order matters: upstream ngtsc pools **content queries first, then
+    // view queries** (compiler/src/render3/view/compiler.ts emits
+    // `contentQueries:` before `viewQuery:` in the metadata object, and
+    // pools predicates in the same order). Reversing this swaps the
+    // `_c<N>` indices visible in the emitted query calls — the runtime
+    // still works either way but the emit diverges from upstream and
+    // breaks goldens / source-anchored tooling.
+    let content_queries_fn = if !content_queries.is_empty() {
         let fn_name = Some(metadata.class_name.as_str());
-        Some(create_view_queries_function(
+        Some(create_content_queries_function(
             allocator,
-            view_queries.as_slice(),
+            content_queries.as_slice(),
             fn_name,
             Some(&mut job.pool),
         ))
     } else {
         None
     };
 
-    // BEFORE template compilation: Pool content query predicates.
-    // Similar to view queries, content query predicates are pooled before template compilation.
-    let content_queries_fn = if !content_queries.is_empty() {
+    let view_query_fn = if !view_queries.is_empty() {
         let fn_name = Some(metadata.class_name.as_str());
-        Some(create_content_queries_function(
+        Some(create_view_queries_function(
             allocator,
-            content_queries.as_slice(),
+            view_queries.as_slice(),
             fn_name,
             Some(&mut job.pool),
         ))