fix(node compat): shake-128, shake-256 aliases for shake128 and shake256 hash algorithms

[lilnasy]

• Fixes Hashing functions from node:crypto don't support the same inputs as Node.js #28442
• Node.js seems to manage these aliases here: deps/openssl/openssl/providers/implementations/include/prov/names.h
• Tested against crypto_hash_test.ts locally against a debug build. The debug build passes, the current stable release fails.

[CLAassistant]

All committers have signed the CLA.

[marvinhagemeister]

LGTM, thanks!

EDIT: Dismissed my review. Looks like somewhere else the aliases need to be wired up too. I'll leave it to @littledivy

a

[lilnasy]

The tests were failing because "shake-128" and "shake-256" were being used as the digest algorithms for testing crypto.pbkdf2. They are not supported for that, not even in Node.js, which is why the tests excluded "shake128" and "shake256" (non-hyphenated) from crypto.getHashes(). Excluding the hyphenated aliases too would pass the test, but the hyphenated aliases don't appear in crypto.getHashes() in Node.js. so I've undone that part instead.

The other test failure looks like a flaky one:

command /home/runner/work/deno/deno/target/release/deno run --quiet --v8-flags=--expose-gc heapstats.js
command cwd /home/runner/work/deno/deno/tests/specs/run/heapstats
output path /home/runner/work/deno/deno/tests/specs/run/heapstats/heapstats.js.out

panicked at tests/specs/mod.rs:442:12:
assertion failed: `(left == right)`

Diff < left / right > :
<Allocated: 7MB
>Allocated: 8MB
 Freed: -8MB

[lilnasy]

@littledivy This is ready to review.