feat(@angular/build): migrate Angular Linker to oxc-parser and magic-string

[clydin]

This refactors the Angular linker processing in the ESBuild pipeline to use oxc-parser and magic-string instead of @babel/core.

By using the lightweight AST and precise token spans provided by OXC, the linker is able to process partial declarations via targeted magic-string overwrites in-place. This removes the dependency on @babel/core and the linker Babel plugin, yielding faster build startup times and improved compilation performance.

[gemini-code-assist]

Code Review

This pull request introduces a high-performance Angular partial declaration linker using oxc-parser and magic-string to replace the Babel-based linker. The review feedback highlights critical compatibility issues with the OXC AST structure. Specifically, oxc-parser does not export a Visitor class, requiring a custom recursive AST walker instead. Additionally, OXC AST node types differ from standard ESTree nodes: generic Literal nodes are represented as specific StringLiteral, NumericLiteral, BooleanLiteral, and NullLiteral nodes; identifiers are split into IdentifierReference and IdentifierName; and object properties are represented as ObjectProperty instead of Property.

[JoostK]

I've been wanting to experiment with this, so I'm excited to see this 🥳

[JoostK]

I don't see anything obviously broken anymore, but the AST builder/parenthesis wrapping is subtle. Keeping the Babel plugin behind an envvar could perhaps be a risk mitigation measure (G3 doesn't have partially compiled code, this is 3P only and thus not as widely covered in a test corpus)