feat: Support XZ decompression

[yujincheng08]

No description provided.

[Pr0methean]

Mostly looks good.

[yujincheng08]

All done

[Pr0methean]

Thanks for your contribution! I'm hoping to merge and release it within the next 24 hours.

[yujincheng08]

CI failed but it seems to come from mainline.

[yujincheng08]

@Pr0methean Hi, I found lzma-rust which supports partial decompression and BCJ, and most importantly, it supports compression. Maybe you are interested in using it instead?

[yujincheng08]

I have an ugly implementation to use lzma-rust here: https://github.com/yujincheng08/zip2/tree/lzma-rust

But it's not panic-free so I am not opening a PR. Maybe you could build upon it.

[Pr0methean]

Opened an issue to consider lzma-rust. I'd still like to merge this change in its current form.

[yujincheng08]

Thanks. It is reasonable to use lzma-rs for now and later migrates to lzma-rust for both lzma and xz (and add compression support).

[Pr0methean]

Update: It may take another day or two to merge this, since I first need to generate new fuzz corpora with smaller inputs so the fuzz tests can run faster, and the scripts I'm using to do so may still need debugging.

[yujincheng08]

I dont think the repo settings are correct here.

According to the github documentation:

The merge queue provides the same benefits as the Require branches to be up to date before merging branch protection, but does not require a pull request author to update their pull request branch and wait for status checks to finish before trying to merge.

If merge queue is set, we dont need to enable Require branches to be up to date before merging. But both are enabled. Thus merge cannot be done once someone push to the target branch.

Also the timeout is not correctly set while a time-consuming fuzz test is checked, and the checks nearly exceeds the time limit of Github Action (6h). If merge queue is set, some status check can be moved to merge queue while PR check can only contain neccessary ones (like format and compilation without unit test).

I think we could disable Require branches to be up to date before merging, disable unit test (at least diable fuzz test) for PR, set merge queue timeout to a longer time.

[Pr0methean]

Actually Require branches to be up to date before merging isn't enabled for this repo -- I've only been rebasing this PR when there turned out to have been test failures from a bug that was already in master. As for a longer merge-queue timeout, GitHub unfortunately only supports a maximum of 6 hours. What I'm trying to do by generating a new fuzz corpus is to ensure that the fuzz test runs fast enough that it usually hits the iteration limit before the time limit.

[Pr0methean]

As for the redundancy of the checks, that's necessary to detect the scenario where two PRs in flight at the same time are compatible with master, but not with each other.