wrpc_transport depending on wasi on wasm target even without "net" feature

Hello, while I was trying to explore using this crate as sort of an early access way of using wasip3's stream/future types by using AsyncReadStream/AsyncWriteStream in wasip2 and dedicating a thread in running the component, I faced compilation errors.

The compilation errors came from https://github.com/bytecodealliance/wasm-tools/issues/2047, and through that, I found that some of my other dependencies was using wasi@0.14 while the wrpc_transport in crates.io still uses wasi@0.13.

Temporarily overriding wrpc_transport to target this repository does fix the compilation (since this repository had already updated deps to wasi@0.14). Still, I think it would be great that wrpc_transport doesn't depend on wasi if "net" is not enabled moving forward.