feat(jsruntime/http): V8-fallback createServer bridge to native

[proggeramlug]

Summary

• Bridges node:http's createServer from the V8/JS-runtime fallback path
  to a real hyper-based HTTP/1.1 server. Pre-fix the stub threw
  http.createServer not supported in this environment, which crashed
  express (and would crash fastify/nestjs the same way) at module init.
• Adds four deno_core ops — op_perry_http_listen (async, binds a
  tokio::net::TcpListener + spawns a hyper accept loop on Perry's
  shared multi-thread tokio runtime), op_perry_http_accept (async,
  pops the next pending request), op_perry_http_respond (sync,
  resolves the response oneshot), op_perry_http_close (sync, drops
  the accept-loop shutdown channel).
• Replaces the node:http JS stub in crates/perry-jsruntime/src/modules.rs
  with a real Server class + minimal IncomingMessage/ServerResponse
  surface (req.method/url/headers, res.writeHead/setHeader/
  write/end/statusCode).
• Fixes a latent "no reactor running" panic by entering Perry's shared
  TOKIO_RUNTIME inside ensure_runtime_initialized and with_runtime
  (and jsruntime_process_pending). Without this, JsRuntime::new's
  captured tokio handle was empty and any subsequent async op that
  touched tokio::net / tokio::spawn panicked.
• Keeps the program alive while any V8-fallback server is listening via
  a new active-server counter wired into jsruntime_has_active_handles.

Goal: enough HTTP server semantics that the prompt-cited express smoke
(app.listen(port, cb) + a single handler that calls res.end) works
end-to-end through the V8 path. Streaming bodies, HTTPS / HTTP/2,
WebSocket upgrades, and req.socket/req.connection are explicitly
out of scope — applications that need them should keep using the
native compile path through perry-ext-http-server. See the CHANGELOG
entry for the full deferred list.

Test plan

• cargo build --release -p perry-runtime -p perry-stdlib -p perry-jsruntime -p perry
• test-files/test_http_createserver_v8.ts (native node:http path) prints 200 hello — unchanged.
• Express prompt smoke: import express from 'express'; app.get(...); app.listen(19000, cb); server.close() prints listening on 19000 and exits 0 (pre-fix: thrown error at module init).
• Middleware-only express variant served a real HTTP response: external fetch returned status=200 body=hi-from-middleware and the handler logged middleware called GET /.
• Byte-for-byte match with node --experimental-strip-types test-files/test_http_createserver_v8.ts (200 hello).