[Cyan4973]

--memory (128 MiB by default) limits the memory used to decompress zstd frames, but it has never applied to .xz and .lzma input: liblzma was initialized without a limit.

This PR passes the limit to liblzma as well. When a file needs more, zstd reports how much memory it needs and suggests a --memory= value, as it already does for zstd frames:

$ zstd -d --memory=1MB big.xz
big.xz : Memory needed by xz/lzma decoder larger than maximum : 67174448 > 1048576
big.xz : Use --memory=65MB

Behavior change: .xz and .lzma files that need more than 128 MiB to decode now require --memory=, like zstd frames with a large window. Files made with the xz presets are not affected: the largest preset (-9, -9e) uses a 64 MiB dictionary and needs 65 MiB to decode.

The man page now says that --memory also applies to .xz and .lzma.

Tests

• New in playTests.sh: .xz and .lzma files with a 4 MiB dictionary are rejected with --memory=1MB. The message suggests --memory=5MB, and that value is then accepted.
• In CI, these tests run in the "CMake build using make wrapper" job, which builds with liblzma.
• Locally, with liblzma: the full playTests.sh and the cli-tests pass. The build also passes with gcc and clang (-Werror) and without liblzma.