fix(ffi): exclude nodedb-lite-ffi from wasm32 targets

Gate the crate's dependencies under
`[target.'cfg(not(target_arch = "wasm32"))'.dependencies]` and add a
top-level `#![cfg(not(target_arch = "wasm32"))]` attribute so the FFI
crate is a no-op when the workspace is compiled for
`wasm32-unknown-unknown`. This prevents C/JNI symbols from being pulled
into the WASM build, which has no use for them.

Author: farhan-syah

nodedb-lite-ffi/Cargo.toml

@@ -12,7 +12,7 @@ homepage.workspace = true
 [lib]
 crate-type = ["lib", "staticlib", "cdylib"]
 
-[dependencies]
+[target.'cfg(not(target_arch = "wasm32"))'.dependencies]
 nodedb-lite = { workspace = true }
 nodedb-client = { workspace = true }
 nodedb-types = { workspace = true }

nodedb-lite-ffi/src/lib.rs

@@ -1,4 +1,5 @@
 //! C FFI bindings for NodeDB-Lite.
+#![cfg(not(target_arch = "wasm32"))]
 //!
 //! Exposes the `NodeDb` trait as C-callable functions for Swift (iOS)
 //! and Kotlin/JNI (Android) interop.