[Detection] Factory-with-arguments in extractFactoryCallAssignments (A5 follow-up)

[AndresL230]

Summary

PR #110's A5 factory pattern recognition handles const c = makeClient() but does NOT handle const c = makeClient(config) — the regex extractFactoryCallAssignments matches no-arg calls only.

Current behavior

// works (resolved):
const client = makeClient();

// not resolved:
const client = makeClient(config);
const client = makeClient({ apiKey: process.env.KEY });
const client = makeClient(env, options);

What to do

• Update extractFactoryCallAssignments in src/ast/cross-file-resolver.ts to match factory calls with any argument count.
• AST-based match is preferable to a wider regex — the existing pattern looks for \bmake[A-Z]\w*\s*\(\s*\) shape; widen to \(\s*[^)]*\s*\) or use the AST call_expression node directly.
• Audit fixture demonstrating zero-arg, single-arg, and multi-arg factories.
• Test ensuring each variant resolves to the factory's factoryReturnMap entry.

Acceptance criteria

• makeClient(config) resolves to the provider that makeClient returns.
• makeClient({ apiKey }) resolves.
• Multi-arg makeClient(a, b, c) resolves.
• No regression to PR fix(detection): A3 + A5 — barrel re-exports + factory/DI/aliased clients (closes #75, #77) #110's zero-arg factory test.
• Benchmark detection recall stays at ≥51.47% (current baseline).

Reference

Memory: a3_a5_pr_status.md — "Factory with arguments (const c = makeClient(config)) — extractFactoryCallAssignments matches no-arg calls only."