Summary

Fix zipfile reading of Zstandard-compressed archive members containing multiple concatenated frames.

ZstdDecompressor intentionally stops after one frame and stores any remaining compressed input in unused_data. ZipExtFile previously treated the decompressor's eof state as the end of the entire ZIP member. As a result, later frames were ignored, which could truncate the returned data or cause an incorrect CRC-32 error.

Fix

When a Zstandard frame ends, ZipExtFile now:

1. Retrieves any remaining compressed input from unused_data.
2. Creates a new ZstdDecompressor for the next frame.
3. Continues with unused_data, or reads more compressed data when the frame boundary falls between archive reads.
4. Marks the ZIP member as finished only after all compressed input and buffered unused data have been consumed.

This keeps the single-frame semantics of ZstdDecompressor unchanged and handles concatenated frames at the zipfile streaming layer.

Tests

The regression test creates a valid Zstandard-compressed ZIP member containing two frames and covers:

• Both frames being available in the same archive read.
• A frame boundary occurring between two archive reads.

• Issue: zipfile.ZipFile fails to read zstd-compressed file consisting of multiple frames #154481