zlib: add zstd support

[jkrems]

Adds ZstdCompress and ZsdDecompress to the zlib module which can be used to compress/decompress with the Zstandard ("zstd") algorithm.

Notable omissions:

• Providing dictionaries isn't implemented.
• The docs in zlib.md don't call out any params beyond the basic compression level.

The code follows similar patterns to the PR that added Brotli support. Just that instead of brotli, it adds the equivalent zstd APIs. Just like Brotli, this required separate compression/decompression context objects.

Zstd itself has been around and stable for multiple years but this PR is early in terms of web support: It only just starts shipping by default in Chrome 123. On the other hand, by shipping in Chrome it will soon be supported quite widely on the web. Firefox also signaled support (https://bugzilla.mozilla.org/show_bug.cgi?id=1301878#c65). Zstd is now enabled on the web and supported by both Chrome and Firefox: https://caniuse.com/zstd

Official support in node.js would allow passing additional WPTs around fetch (nodejs/undici#2847).

[nodejs-github-bot]

Review requested:

• @nodejs/security-wg

[jkrems]

Alright, got up to making the basics (seemingly) work:

$ out/Debug/node -p 'zlib.zstdDecompressSync(zlib.zstdCompressSync("Hello World")).toString()'
Hello World

[jasnell]

@jkrems ... can you give this a rebase?

[jkrems]

@jasnell I can but at this point I have spent quite bit of time on this PR without a clear signal on whether this would be likely to land (in this form or another). So it would be easier to justify if there was a tentative "yep, the high level approach looks good". By high level I mean something like "roughly following brotli integration in terms of API, using the facebook zstandard native implementation as the backing".

[bricss]

That's will be great to have this in a main branch 🌿after all 🫠

[KhafraDev]

@nodejs/tsc There aren't any outstanding objections, but this PR does appear to be at an impasse. @jkrems did not receive an answer to their question #52100 (comment). I have held off for months from doing this, hoping someone could review and collaborate since I couldn't.

[marco-ippolito]

Nobody reviewed and approved the PR, there is nothing officially blocking it. If someone wants to volunteer to review it and approve it without objections, then its gonna land.
I don't think there is anything the TSC can do about it, or to be discussed TSC side

[KhafraDev]

Maybe not, but I don't think I'm in a position to give guidance or give definitive instructions on the approach. I have pinged the zlib team, I pinged the security team, I have asked people to review it in private, so I didn't know what else to do lol.

[anonrig]

I'm interested in landing this PR as well. If we can have one last push (and rebase this PR), I'm more than happy to review and land this PR.

[jkrems]

@anonrig Thanks! I'll work on a rebase.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/65051/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/65052/

[nodejs-github-bot]

Landed in 0782c91...bf12d72