fix: #770 — wire net.connect(options, cb) and emit Error objects

[TheHypnoo]

Summary

Closes #770 (split off from #767 case 4).

net.connect({ host, port }, cb) — the standard Node.js options-object overload — failed with "file name contained an unexpected NUL byte" because the codegen dispatch entry only accepted the positional net.connect(port, host) form. With args: &[NA_F64, NA_STR] the second arg (the callback closure) was coerced through js_get_string_pointer_unified, the runtime read garbage bytes from the closure's memory as the hostname, and getaddrinfo's internal CString::new() blew up.

Separately, the 'error' event emitted raw NaN-boxed strings instead of Error-shaped objects, so socket.on('error', err => err.message) came back as undefined.

What changed

• Codegen dispatch (crates/perry-codegen/src/lower_call.rs): net.connect / net.createConnection now declare args: &[NA_F64, NA_F64, NA_F64] (3 slots, both overloads supported). The runtime sees raw NaN-boxed bits and discriminates by tag.
• perry-ext-net (crates/perry-ext-net/src/lib.rs) and perry-stdlib (crates/perry-stdlib/src/net/mod.rs, for the PERRY_DISABLE_WELL_KNOWN=1 path):
  • js_net_socket_connect(arg1_f64, arg2_f64, arg3_f64) detects whether arg1 is a NaN-boxed object pointer (POINTER_TAG = 0x7FFD — narrow check that cleanly rejects undefined padding) or a regular f64 number. Plain ports like 80.0 never carry the quiet-NaN prefix.
  • For the options form, extract host / hostname / port from the object via the runtime's js_object_get_field_by_name_f64.
  • Auto-register the optional connectListener in both forms:
    • net.connect({host, port}, cb) → cb comes through arg2
    • net.connect(port, host, cb) → cb comes through arg3
  • 'error' events now ship an Error-shaped object { message: msg } so err.message works. Falls back to a bare string on alloc failure.
• Manifest (crates/perry-api-manifest/src/entries.rs): widened net.connect / net.createConnection to declare 3 params to satisfy the dispatch/manifest drift guard, plus regenerated docs/api/perry.d.ts.

Test

New fixture test-files/test_net_connect_options.ts chains sock1 (options) → sock2 (positional) → sock3 (closed-port error) so parity output order is deterministic against node --experimental-strip-types:

server listening
sock1 (options): connectListener fired
sock2 (positional): connectListener fired
sock3 error typeof: object
sock3 error message typeof: string
sock3 error has message: yes
done

cargo test --release -p perry-codegen --test manifest_consistency -p perry-ext-net -p perry-stdlib --lib — all green. Regression-checked fetch / axios (still work) and the original net.connect(port, host) positional form (still works).

Test plan

• test-files/test_net_connect_options.ts matches Node's output byte-for-byte
• User repro from net.connect(options, cb) options-object overload corrupts host string (NUL byte) #770 (net.connect({host: 'X', port: N}, cb)) connects and fires the connectListener
• net.connect(port, host, cb) also fires the connectListener
• 'error' listener receives object with usable .message on closed port
• fetch / axios continue to return 200
• cargo test --release -p perry-codegen --test manifest_consistency -p perry-ext-net -p perry-stdlib --lib passes
• CI parity / cargo-test / lint / compile-smoke green