Emit an any for namepath types

[weswigham]

Fixes #36690

When we added an AST node to parse over namepaths in #32563, we didn't add any checker code to handle the new type node anywhere - in many cases, this meant a fallback to the errorType (which is fine), but here we needed to explicitly map the namepath type node into an any type node.

[sandersn]

Fix makes sense here -- should we also add a general fallback to these specific early exit?

[weswigham]

should we also add a general fallback to these specific early exit?

? what do you mean?

[orta]

Thanks! Feels alright to me

[sandersn]

Yikes, I mangled that sentence! What I meant was: the function has an early exit for specific cases. Should it also have a general fallback at the bottom sort of like we give errorType when type checking? (That's a question for future work anyway; the code as-is is good as a bug fix.)

[weswigham]

Should it also have a general fallback at the bottom sort of like we give errorType when type checking?

It has a "fallback" already - emit the node as-is, which is used for most typenodes. We only map away jsdoc-y typenodes here, cause printing them in not jsdoc is probably wrong. Namepath is even more special in that it doesn't even have emitter code, so actually just printed as an empty string.