fix(compiler-cli): record class extends clause references in DeferredSymbolTracker - #70111

Problem

DeferredSymbolTracker.lookupIdentifiersInSourceFile prunes ts.isTypeNode subtrees so that references appearing exclusively inside type annotations do not prevent static import declarations from being elided in favor of @defer dynamic import()s.

However, ts.isTypeNode returns true for ts.ExpressionWithTypeArguments, which TypeScript's AST uses to represent both extends and implements heritage clauses. An extends clause on a class declaration or class expression is a runtime value position that survives into emitted JavaScript:

import { DeferredComponent, BaseComponent } from './components';

@Component({
  template: `
    @defer {
      <defer-cmp />
    }
  `,
  imports: [DeferredComponent],
})
export class MyComponent extends BaseComponent {}

Because isTypeNode returned true for ts.ExpressionWithTypeArguments, references to BaseComponent were pruned. DeferredSymbolTracker concluded that BaseComponent had zero runtime references, marked the static import as deferrable, and deleted it from the emitted JavaScript output.

At runtime, this results in a fatal ReferenceError: BaseComponent is not defined.

Solution

Ensure that ExpressionWithTypeArguments representing an extends clause on a class declaration or class expression is not treated as an erasable type node in lookupIdentifiersInSourceFile. References within a class extends clause are now properly recorded as active runtime references, preventing the static import from being deleted when a base class is referenced.

Testing

Added a new compliance test case in packages/compiler-cli/test/compliance/test_cases/r3_view_compiler_deferred/:

• defer_extends_clause verifying that static imports are preserved and the dependency is emitted eagerly when a sibling symbol is referenced in a class extends clause.