fix: #769 — wire node:http / node:https client request through codegen dispatch

[TheHypnoo]

Summary

Closes #769 (split off from #767 case 3).

http.request(...) and http.get(...) (and the https.* variants) always returned undefined from compiled TypeScript, so the standard const req = http.request(url, cb); req.on('error', ...); req.end() pattern crashed at .on with "Cannot read properties of undefined". The runtime implementations existed in perry-ext-http and the FFI symbols were declared, but no NativeModSig entries existed in the codegen dispatch table — calls fell through to the unknown-method path and got back TAG_UNDEFINED.

What changed

• Codegen dispatch (crates/perry-codegen/src/lower_call.rs): add NativeModSig entries for http.request, http.get, https.request, https.get and the ClientRequest instance methods on, end, write, setHeader, setTimeout.
• HIR class tagging (crates/perry-hir/src/lower.rs + crates/perry-hir/src/lower_decl.rs): tag const req = http.request(...) | http.get(...) | https.* bindings as ("http", "ClientRequest") so req.on/.end/... dispatch through the new class-filtered entries. Mirrors the existing net.createConnection / tls.connect tagging. Important: the closure-body path in lower_decl.rs had no equivalent of the top-level arm in lower.rs, so request() inside a callback (the common shape: server.listen(..., () => { ... request(...) ... })) was unreachable.
• perry-ext-http (crates/perry-ext-http/src/lib.rs):
  • accept either a URL string or an options object in request_common — the previous code only handled the options-object overload, and the reporter's repro uses http.request("http://...", cb);
  • rewrite dispatch_request to spawn the reqwest future as a detached task on the multi-thread runtime instead of Handle::current().block_on. Now that the dispatch actually reaches this code, block_on panicked with "Cannot start a runtime from within a runtime" because spawn_blocking_with_reactor runs the closure inside runtime().spawn(async {...}). Mirrors the spawn_socket_runner pattern in perry-ext-net, including the LTO black_box workaround for tokio's CONTEXT statics;
  • export js_http_is_incoming_message(handle) so perry-stdlib can gate property dispatch on registry membership.
• IncomingMessage property dispatch (crates/perry-stdlib/src/common/dispatch.rs): add a statusCode / statusMessage / headers arm in js_handle_property_dispatch. Without this, (res) => res.statusCode inside the response callback returned undefined.
• Client-side pump (crates/perry-stdlib/Cargo.toml + crates/perry-stdlib/src/common/async_bridge.rs + crates/perry/src/commands/compile/optimized_libs.rs): add an external-http-client-pump feature, drain js_http_process_pending from the main-thread pump, and keep the event loop alive via js_http_has_pending while a request is in-flight. Activated by the well-known flip whenever node:http / node:https route to perry-ext-http. Mirrors the existing external-http-server-pump plumbing.

Test

New fixture test-files/test_node_http_client_request.ts exercises all three forms (request(url, cb), request(options, cb), get(url, cb)) against an in-process createServer and verifies res.statusCode reflects the response. End-to-end verified against http://example.com/:

statusCode: 200
statusMessage: OK
typeof headers: object
content-type header: text/html

The reporter's exact req.on/req.end repro from #769 also runs without crashing.

cargo test --release -p perry-hir -p perry-codegen -p perry-ext-http --lib — all green. Regression-checked fetch/axios (still work) and net.connect(options, cb) (still fails — tracked separately in #770).

Test plan

• test-files/test_node_http_client_request.ts runs locally on macOS arm64
• res.statusCode / res.statusMessage / res.headers return real values against an external server
• fetch / axios continue to return 200
• cargo test --release -p perry-hir -p perry-codegen -p perry-ext-http --lib passes
• CI parity / cargo-test / compile-smoke green