deleteDeclaration: don't crash on the top node.

A misbehaved client can sometimes cause the server to reach
`deleteDeclaration` with the SourceFile, and it will crash due to no
`node.parent`.  I couldn't find a good way to create a test for it, but
I could trigger it manually by having a file with just a `,`, and
sending an explicit `getCodeFixes` command to the server with
`errorCodes: [6133]`.

I can only guess some scenario in which Emacs or other editors could
lead to that, but it's easy to just avoid the crash instead.  (Doing the
default of deleting the whole thing -- not really important since it's a
broken client situation anyway--?)

Fixes microsoft#33726

Author: elibarzilay

src/services/textChanges.ts

@@ -1361,7 +1361,10 @@ namespace ts.textChanges {
                     break;
 
                 default:
-                    if (isImportClause(node.parent) && node.parent.name === node) {
+                    if (!node.parent) {
+                        // a misbehaving client can reach here with the SourceFile node
+                        deleteNode(changes, sourceFile, node);
+                    } else if (isImportClause(node.parent) && node.parent.name === node) {
                         deleteDefaultImport(changes, sourceFile, node.parent);
                     }
                     else if (isCallExpression(node.parent) && contains(node.parent.arguments, node)) {