getParentIfKindOrThrow throws on CallExpression syntax

**Describe the bug**

Version: 20.0.0

Error received: "Error: The parent was not a syntax kind of CallExpression."

When using `getParentIfKindOrThrow`, this sometimes throws on the `callExpression` syntax. This seems to occur depending on the length of the script.

**To Reproduce**

```ts
import { Project } from "ts-morph";

const generateSourceFile = (script: string): SourceFile => {
const project = new Project({
useInMemoryFileSystem: true
});
project.createSourceFile("script.ts", script)

const sourceFile = project.getSourceFileOrThrow("script.ts");
return sourceFile;
}

// This script throws...
const script = `declare function getSomeField(id: string): boolean;getSomeField(“abcdefg wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww”);`

const sourceFile = generateSourceFile(script);
const func = sourceFile.getFunction("getSomeField");

try {
const getFieldByIdNodes = func?.findReferencesAsNodes();
for(const node of getFieldByIdNodes) {
const callExpression = node.getParentIfKindOrThrow(SyntaxKind.CallExpression);
....
}
} catch (err) {
console.log(error);
}

```
But updating `script` to be:
const script = `\n declare function getSomeField(id: string): boolean;getSomeField(“abcdefg wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww”); \n`

Then it no longer throws.

Also adding in a few extra characters into the script such as:

const script = `declare function getSomeField(id: string): boolean;getSomeField("abcdefg wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww zz");` results in it no longer throwing too.

Why would wrapping this in newline stop it from throwing?

Start with CONTRIBUTING.md and run the TypeScript reproduction using the two script variants shown in the issue. Trace the node returned by findReferencesAsNodes() and the getParentIfKindOrThrow entry point to determine why the parent differs. Done means the reported case is handled consistently and the reproduction no longer throws.

Written by the indexing model from the issue text.