fix(extractor): recognize inline-new expression as receiver type in extractReceiverName

When the object of a member call is a `new_expression` (e.g. `new Dog().bark()`)
or a parenthesized `new_expression` (e.g. `(new Dog('Rex')).bark()`),
`extractReceiverName` now returns the constructor name (e.g. `'Dog'`) directly
instead of the raw node text (e.g. `'(new Dog(\'Rex\'))')`).

This lets the resolver reach the direct qualified method lookup path
(`Dog.bark`) without relying on the text-based regex heuristic that was
handling these expressions in `call-resolver.ts`.

Closes #1396

Author: carlos-alm

src/extractors/javascript.ts

@@ -2516,6 +2516,21 @@ function extractReceiverName(objNode: TreeSitterNode | null): string | undefined
   if (!objNode) return undefined;
   const t = objNode.type;
   if (t === 'identifier' || t === 'this' || t === 'super') return objNode.text;
+  // `(new Foo(...)).method()` — extract the constructor name so the resolver can
+  // look up `Foo.method` directly without relying on a text-based regex heuristic.
+  if (t === 'new_expression') {
+    const name = extractNewExprTypeName(objNode);
+    if (name) return name;
+  }
+  if (t === 'parenthesized_expression') {
+    for (let i = 0; i < objNode.childCount; i++) {
+      const child = objNode.child(i);
+      if (child?.type === 'new_expression') {
+        const name = extractNewExprTypeName(child);
+        if (name) return name;
+      }
+    }
+  }
   return objNode.text;
 }