fix(rivetkit-napi): vendor openssl on all linux targets

The prior arm64-gnu-only scope still left linux-x64-gnu dynamically linked
to libssl.so.1.1 from the bullseye builder base, breaking consumers on
Debian 12+ / Ubuntu 22.04+ / any host without OpenSSL 1.1. Widen to all
linux targets so the .node has no runtime libssl dependency.

Author: NathanFlurry

Cargo.lock

@@ -33,9 +33,13 @@ napi-build = "2"
 [dev-dependencies]
 serde_bare.workspace = true
 
-# Force vendored openssl for the aarch64-linux-gnu cross build. The linux-gnu
-# builder image ships x86_64 libssl-dev only, so transitive openssl-sys (via
-# reqwest/native-tls pulled in by opentelemetry-http) cannot find arm64 headers
-# through pkg-config. Vendoring compiles openssl from source instead.
-[target.'cfg(all(target_arch = "aarch64", target_env = "gnu"))'.dependencies]
+# Statically link openssl on all Linux targets. transitive openssl-sys (via
+# reqwest/native-tls pulled in by opentelemetry-http) would otherwise pick up
+# whatever libssl the builder image happens to ship, and the resulting `.node`
+# inherits a NEEDED libssl.so.X runtime dependency that breaks on hosts with a
+# different openssl (e.g. linking to libssl.so.1.1 on Debian bullseye breaks on
+# Debian bookworm / Ubuntu 22.04+). Vendoring compiles openssl from source and
+# static-links it into the addon. darwin uses Security.framework and windows
+# uses schannel, so they don't need this.
+[target.'cfg(target_os = "linux")'.dependencies]
 openssl = { version = "0.10", features = ["vendored"] }