node:zlib: don't abort when the native handle is driven outside the zlib.ts lifecycle - #32762

`init()` now checks `closed` but still doesn't check `write_in_progress` / `pending_close`, so `h.write(...); h.init(...)` runs `stream.with_mut(|s| s.init(...))` on the JS thread while the worker thread is inside `stream.with_mut(|s| s.do_work())` — two concurrent `&mut Context` on the same `JsCell` (no runtime borrow check), i.e. `deflateInit2_` racing `deflate()` on the same `z_stream`. This is pre-existing, but it's the same out-of-lifecycle abort class this PR is closing and the new `throw_

The `set_params`-failure branch here calls `s.close()` (which sets `mode = NONE` and frees the encoder) but never sets `self.closed`, so `throw_if_closed` still passes afterward. A subsequent `writeSync()` then survives the new `state.is_none()` guard in `do_work()` only to abort in `get_error_info()`'s `_ => unreachable!()` arm (mode is `NONE`); a second `init()` likewise hits `Context::init`'s `_ => unreachable!()`. `NativeZstd::init` has the same gap. Adding `self.closed.set(true)` next to `s