fix: setClassMetadata ctor params use namespace-prefixed types for imported deps

[Brooooooklyn]

Constructor parameter types in ɵsetClassMetadata were using bare names (e.g., SomeService) instead of namespace-prefixed references (e.g., i1.SomeService) for imported types. TypeScript erases type annotations at runtime, so imported types need namespace imports to remain available.

The fix passes constructor dependency metadata and the namespace registry into build_ctor_params_metadata, and adds build_param_type_expression which uses namespace prefixes when the type annotation name matches the dep token name and the dep has a source module. When they differ (e.g., @Inject(DOCUMENT) doc: Document), falls back to bare name.

---

Note

Medium Risk
Changes codegen for setClassMetadata ctor parameter metadata and relies on constructor dependency metadata/namespace assignment, which could affect emitted JS and import generation. Scope is limited and covered by new integration tests for common @Inject edge cases.

Overview
build_ctor_params_metadata now accepts constructor dependency metadata plus a NamespaceRegistry and emits namespace-prefixed type references for imported constructor param types (e.g., i1.SomeService) to match Angular when TS types are erased at runtime.

The transform pipeline now passes constructor_deps/registry into class metadata emission, exports NamespaceRegistry from the crate API, and updates the NAPI class-metadata helper to provide a registry (without deps, so it won’t prefix in that standalone path). New integration tests assert correct prefixing, including @Inject(SomeService) and a fallback when the inject token differs from the type (e.g., DOCUMENT vs Document).

^{Written by Cursor Bugbot for commit efe376a. This will update automatically on new commits. Configure here.}