fix(compiler): track type query references

[Boulea7]

What is the current behavior?

Class and enum names used in identifier-based keyof typeof prop types are not collected as type references. As a result, generated components.d.ts files can omit required imports. Aliases and re-exports can also produce incorrect imports or colliding docs type-library IDs.

GitHub Issue Number: Fixes #2482

What is the new behavior?

The compiler now collects identifier-based TypeQueryNode references when they resolve to classes or enums. It preserves local, named, default, and re-exported aliases in generated component declarations, supports multiple local names for the same default export, and derives docs type-library IDs from the resolved declaration source.

Documentation

N/A. This is a compiler fix covered by regression tests.

Does this introduce a breaking change?

• Yes
• No

Testing

• npm run test.jest -- src/compiler/transformers/test/parse-props.spec.ts --runInBand (48 tests)
• npm run test.jest -- src/compiler/transformers/test --runInBand (356 tests)
• npm run test.jest -- src/compiler/types/tests/generate-app-types.spec.ts --runInBand (16 tests, 16 snapshots)
• npm run tsc.prod
• npm run lint
• npm run prettier.dry-run
• npm run build

Other information

Qualified namespace expressions are outside this change's scope; this addresses identifier-based enum and class queries such as the one reported in #2482.

[johnjenkins]

looks great - tysm!

Few little bits. More generally, I noticed you removed some of the (now outdated) comments describing the branching variations etc. Can you make sure to replace with updated ones, seeing as the branching logic - if anything - is slightly more opaque / subtle now. Nothing too long - just simple pointers 🙏

[johnjenkins]

@Boulea7 - my-bad ... need to normalise the path before it touches sys e.g.

import { join as pathJoin, resolve } from 'path';
...
const join = (...segments: string[]) => normalizePath(pathJoin(...segments), false);

Additionally, you now need to restore cwd

     const compiler = await createCompiler({ ...config, tsconfig: tsconfigPath });
+    const originalCwd = process.cwd();
     try {
       const results = await compiler.build();
       ...
     } finally {
+      process.chdir(originalCwd);
       await compiler.destroy();
     }

[Boulea7]

Windows was reading the docs output through an unnormalized backslash path, so the mock filesystem lookup returned undefined. The fixture now normalizes every joined path before it reaches the mock system and restores the original cwd before compiler teardown. The focused regression and full unit suite pass; lint, formatting, and build pass as well.