feat(ext/node): support http2session.socket

[seanmonstar]

Continues from #22617

Closes #20903

cc @bartlomieju @satyarohith

[seanmonstar]

I'm not fully clear on the semantics of Deno <=> Rust ownership, so I don't know if this is easily shared. But if it is, I can just make the change lower in this file:

     this.on(
       "connection",
       (conn: Deno.Conn) => {
         try {
-          const session = new ServerHttp2Session();
+          const session = new ServerHttp2Session(conn);
           this.emit("session", session);
           this.#server = serveHttpOnConnection(
             conn,

[bartlomieju]

This should be okay to do; "Deno.Conn" is a resource backed by a Rust resource. If the Rust resource is moved the worst we get is BadResource error in JS, which seems preferable than not having connection available on the session object at all.

[seanmonstar]

I spoke too eagerly, it seems there isn't a straight forward way to create a net.Socket from a Deno.Conn, or if there is I haven't found it.

[satyarohith]

Yes. We have to refactor net.Socket to work on top of rust resource that backs Deno.Conn. We can do that in a future iteration.

[satyarohith]

LGTM - thanks @seanmonstar!