Build issues with unmaintained `xz2` crate

[ctron]

Describe the bug

It looks like zip got some xz support recently. However, it using xz2 crate, which hadn't seen any update in 3 years. Others moved on, and use the liblzma crate, which is maintained: https://crates.io/crates/liblzma

The problem is, that if both xz2 and libzma end up in a build tree, Rust can't compile this, as two crates use the same native library.

To Reproduce

Use zip and liblzma in the same project.

Expected behavior

There should be way to seamlessly use both.

I'd expect to either use a more maintained version (like liblzma 0.3). Or allow choosing between either using feature flags.

Additional context

It is possible to use default-features = false and then enable all features (except xz) one by one.

[Pr0methean]

This will be fixed shortly in 4.0.0, which will be a major-version bump only because the dependency-implied feature flags are being removed (i.e. one could theoretically have a dependency on zip = { version = "3", features = ["xz2"] } that would be broken by the change without the version bump), because I was unaware of the dep: solution until today.

[Pr0methean]

Fixed in 4.0.0.