fix(ext-http-server): defer 'listening' emit + listen callback to the event-loop tick; bind this=server in request handlers (#4903)

[proggeramlug]

Summary

Fixes #4903 — the keystone of the node:http/https runtime-fail tail (#2132).

Node never invokes the listen(port, cb) callback synchronously from inside listen(): the 'listening' event is emitted on a later event-loop tick, after the current synchronous script segment finishes. Perry fired it inline, so the canonical corpus shape

const server = http.createServer().listen(0, () => {
  const port = server.address().port;   // `server` still unassigned → TypeError
});

ran the callback before the const server assignment completed and threw Cannot read properties of undefined (reading 'address'). The address() method itself and the synchronous ephemeral-port bind were already correct since #2132 — the issue's "address() returns undefined" was really "server is undefined".

Changes (crates/perry-ext-http-server/, http + https + http2 listen paths)

• listen() now records a pending 'listening' emit and registers the callback as a once 'listening' listener — Node's exact mechanism, so the emit order vs. listeners added before/after listen() matches (pre-registered → listen callback → late-registered), and 'listening' listeners registered after listen() returned still fire.
• The main-thread pump (js_node_http_server_process_pending) drains the pending emit at the top of each tick, firing every callback with implicit this bound to the server. The queue is detached before any callback runs (re-entrant listen() can't double-fire), server_is_active keeps the event loop alive while an emit is queued, and the GC root scanner pins the queued closure pointers.
• 'request' listeners and the createServer(handler) handler are now also invoked with this = server (Node's emitter semantics), so the corpus function (req, res) { this.address().port } handler idiom works. The binding wraps only the synchronous call; microtasks run outside it.

Validation

Of the 18 corpus tests listed in #4903 (Node v22 test/parallel, run via the scripts/node_core_subset.py staging):

• Now pass byte-for-byte: test-http-agent-null, test-http-client-encoding, test-http-host-headers.
• Every other one now gets past the listen/address wall and fails on a documented sibling-ticket class instead: node:http: Agent/ClientRequest/IncomingMessage/ServerResponse not constructable via new #4904 (new of internal classes), node:http: missing server/timer/socket lifecycle methods (closeAllConnections, setTimeout, timer.unref, ...) #4905 (missing req/socket methods), node:https: client rejects self-signed test certs; rejectUnauthorized/ca/checkServerIdentity not honored #4906 (https self-signed-cert rejection), node:http/https: 89 tests exit non-zero with no output (triage; likely server-hang/framing, partly cascades from #4903) #4909 (hangs), node:http: 2 remaining byte-level diffs (timeout-overflow, many-ended-pipelines) — final piece of #2132 original scope #4910 (byte diffs).
• The pre-existing chained + async-res.end exit-hang reproduces with main's binary too (non-chained shape exits cleanly on both) and stays with node:http/https: 89 tests exit non-zero with no output (triage; likely server-hang/framing, partly cascades from #4903) #4909.
• await new Promise(r => server.listen(0, r)) (axios.get + node:http: process hangs after server.close() — event loop never drains #604 shape) still resolves correctly.
• Existing http test-files (test_http_createserver_v8, test_issue_2153_http_typed_feedback_dispatch, test_issue_2533_aliased_http_createserver, test_node_http_client_request, test_issue_2208_http_inline_request_chain, test_issue_1124_http_buffer_body) behave identically to main.
• New e2e regression test crates/perry/tests/issue_4903_listen_callback_deferred.rs covers the chained shape, deferred-emit ordering, late 'listening' registration, and this-binding in both the listen callback and the request handler.
• cargo test -p perry-ext-http-server green; fmt / file-size / GC store-site / addr-class lint gates green.

A full http+https corpus sweep against the pinned Node v22 corpus is running; I'll post the pass-delta vs the #2132 baseline (38/448) as a follow-up comment.

Per the external-metadata convention, no version bump / changelog entry in this PR — to be folded in at merge time.