Do not compile unsafe FFI code when using Rust backend

[Shnatsel]

flate2 includes plenty of unsafe code that's only used for interaction C backends, and can be omitted from the Rust backend builds. We should use conditional compilation to leave it out of the build when it's not in use, so that any auditing or refactoring efforts can focus on the unsafe code that's actually executed.

For example, the entirety of src/ffi/c.rs can be left out of builds that use Rust backend only; this brings down the unsafe expression count from 107 to 43 according to cargo-geiger.

[Shnatsel]

I've taken a stab at this, but the easy solution from here didn't work (likely due to 2018 edition module changes), and the module reexport hack described here is a bit over my head.

[JohnTitor]

Has it been fixed in the current code?

flate2-rs/src/ffi/mod.rs

Lines 37 to 46 in fe15e4d

	// Default to Rust implementation unless explicitly opted in to a different backend.
	#[cfg(feature = "any_zlib")]
	mod c;
	#[cfg(feature = "any_zlib")]
	pub use self::c::*;
	#[cfg(not(feature = "any_zlib"))]
	mod rust;
	#[cfg(not(feature = "any_zlib"))]
	pub use self::rust::*;