fix(parity): native C# engine finds extra call edges not detected by WASM in build-parity test

[carlos-alm]

Problem

The build-parity integration test tests/integration/build-parity.test.ts > Build parity: native vs WASM — csharp Repository fails locally with the native engine finding 2 extra call edges that WASM doesn't produce.

Details

Native engine finds these additional edges:

{ kind: 'calls', source_name: 'Validators.ValidateUser', target_name: 'Validators.IsValidEmail' }
{ kind: 'calls', source_name: 'Validators.ValidateUser', target_name: 'Validators.IsValidName' }

The roles also differ:

• Native: Validators.IsValidName → dead-ffi, Validators.ValidateUser → core
• WASM: Validators.IsValidName → leaf, Validators.ValidateUser → utility

Impact

Pre-existing failure unrelated to current PR work. The WASM extractor is missing the call edges that the native engine correctly finds. Per project rules, this is a bug in the less-accurate engine (WASM), not an acceptable parity gap.

Discovered in

Noticed while sweeping PR #1415 (fix/inline-new-receiver-1396). The PR only touches JavaScript extraction in src/extractors/javascript.ts — this failure pre-dates it.