Fix find-refs crash on JSDocNamepath (microsoft#36941)

JSDocNamepaths span a lot of identifiers that we don't actually care
about, so it's incorrect for createChildren to add its children as
synthetic nodes.

Author: sandersn

src/compiler/utilitiesPublic.ts

@@ -2469,7 +2469,7 @@ namespace ts {
 
     /** True if node is of a kind that may contain comment text. */
     export function isJSDocCommentContainingNode(node: Node): boolean {
-        return node.kind === SyntaxKind.JSDocComment || isJSDocTag(node) || isJSDocTypeLiteral(node) || isJSDocSignature(node);
+        return node.kind === SyntaxKind.JSDocComment || node.kind === SyntaxKind.JSDocNamepathType || isJSDocTag(node) || isJSDocTypeLiteral(node) || isJSDocSignature(node);
     }
 
     // TODO: determine what this does before making it public.

tests/baselines/reference/renameJSDocNamepath.baseline

@@ -0,0 +1,7 @@
+/*====== /tests/cases/fourslash/renameJSDocNamepath.ts ======*/
+
+/**
+ * @type {module:foo/A} x
+ */
+var x = 1
+var [|RENAME|] = 0;

tests/cases/fourslash/renameJSDocNamepath.ts

@@ -0,0 +1,11 @@
+// @noLib: true
+
+/// <reference path='fourslash.ts'/>
+
+//// /**
+////  * @type {module:foo/A} x
+////  */
+//// var x = 1
+//// var /*0*/A = 0;
+
+verify.baselineRename("0", {});