Resolve aliases in resolveEntityName until we find the given meaning

[ahejlsberg]

Fixes #4038.

[Copilot]

Pull request overview

Fixes a checker alias-resolution edge case in resolveEntityName that could stop too early along an alias chain and return a symbol without the requested meaning (e.g. type meaning), which surfaced as TS2315 in a CommonJS + JSDoc generics scenario.

Changes:

• Update Checker.resolveEntityName to repeatedly resolve aliases until a symbol with the requested meaning is found (or alias resolution stops).
• Add a new compiler test reproducing the CommonJS module.exports + require() + JSDoc generic typedef scenario.
• Add new reference baselines (.types, .symbols) for the added test.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
internal/checker/checker.go	Resolve alias chains in resolveEntityName until the requested meaning is reached, avoiding premature stop at merged symbols.
testdata/tests/cases/compiler/cjsExportGenericTypes.ts	New regression test covering the TS2315 scenario with multiple @template tags and CJS export/require.
testdata/baselines/reference/compiler/cjsExportGenericTypes.types	Reference .types baseline for the new test.
testdata/baselines/reference/compiler/cjsExportGenericTypes.symbols	Reference .symbols baseline for the new test.