Fix stack overflow in error generation for recursive mapped types

[hamzax180]

Fixes #63090

Bug Description

When a mapped type contains a deeply recursive or circular reference, TypeScript correctly identifies it as an error. However, when generating the diagnostic message (Type_of_property_0_circularly_references_itself_in_mapped_type_1), the compiler calls typeToString(mappedType) to format the error text.

Evaluating typeToString(mappedType) triggers property resolution, which evaluates the symbol's type by calling getTypeOfMappedSymbol again. Since symbol.links.type hasn't been cached with the errorType yet, this hits the same circularity, which attempts to throw another error, triggering typeToString again, leading to an infinite cycle and an eventual RangeError: Maximum call stack size exceeded.

Fix Explanation

This PR breaks the infinite recursion by eagerly caching symbol.links.type = errorType; immediately before calling error(...) and typeToString(mappedType).

When typeToString evaluates the mapped type, it now sees the cached errorType for the symbol and safely halts recursion, generating the correct error message without blowing up the call stack.

Testing

Added the provided reproduction from the issue as a compiler test case:

• tests/cases/compiler/issue63090.ts
• Ran hereby baseline-accept so the baseline error generation accurately outputs the circularity error instead of crashing.

[hamzax180]

@microsoft-github-policy-service agree

[hamzax180]

all wishes