fix(node:http,https): Server() callable alias + sync bind for address().port (#2132)

[proggeramlug]

Summary

Two related fixes for the runtime-fail cluster in #2132 (stacked after PR #2184):

1. http.Server(handler) / https.Server(opts, handler) are now callable. Node treats Server and createServer as interchangeable — the same constructor backs both, with or without new. Many Node test fixtures use the callable form. Without a dispatch row, Perry returned undefined and the next .listen(...) crashed with Cannot read properties of undefined (reading 'listen'). Adds Server rows to the codegen native table aliased to js_node_http_create_server / js_node_https_create_server.

2. server.address().port returned the requested port. The listen() FFI wrote bound_port = port (e.g. 0) and then spawned an async task to actually TcpListener::bind(...).await. The listen(port, cb) callback fired before the async bind resolved, so server.address().port inside the callback was the pre-OS-assignment port — 0 for listen(0, cb). Downstream http.get({ port: 0, ... }) then couldn't reach the server. Bind synchronously with std::net::TcpListener::bind, capture local_addr().port(), write the actual port into bound_port, then hand the listener to tokio::net::TcpListener::from_std for the async accept loop.

Same fix mirrored across http, https, and http2 server FFIs. The synchronous bind also matches Node's observable timing: the listen() callback runs after the socket is actually bound.

Verified

• cargo test --release -p perry-ext-http-server --lib: 8 passed.
• cargo fmt --all -- --check: clean.
• Direct re-run of the 4 cited "Cannot read 'listen'" diff tests against local radar staging:
  • test-https-agent.js: was runtime-fail, now pass.
  • test-https-agent-servername.js: was runtime-fail, now pass.
  • test-https-agent-additional-options.js: was runtime-fail, now pass.
  • test-http-abort-client.js: moves past listen crash to surface a distinct downstream gap (serverRes.on undefined) — separate follow-up.

Scope

Second cluster from #2132 after the PEM-Buffer cluster in #2184. Remaining buckets surfaced by the radar (Agent.getName / addRequest missing methods, (no output) silent exits, UnsupportedCertVersion cert-fixture incompat) will be follow-up PRs.

Test plan

• cargo test --release -p perry-ext-http-server --lib
• cargo fmt --all -- --check
• Local node-core radar comparison on the 4 cited diff tests
• CI green