crypto: fix SHAKE128/256 breaking change introduced with OpenSSL 3.4

[panva]

Background:

• This bug surfaces when using linked OpenSSL >= 3.4
• OpenSSL removed default digest lengths for SHAKE128 and SHAKE256 in Set secure defaults for the SHAKE 128/256 digest output length. openssl/openssl#23877 (first appeared in 3.4)
• Before we had 3.5 in CI test: make test-crypto-hash compatible with OpenSSL > 3.4.0 #56160 skipped the tests that would break and let us know, @nodejs/crypto was not pinged there

This PR:

• Adds a --pending-deprecate doc-only deprecation for creating SHAKE128/256 digests without an explicit output length
• Reinstantes pre-3.4 defaults in crypto.createHash()
• Pushes shake128/256 digests from crypto.hash() through crypto.createHash().update().digest() until crypto: support outputLength option in crypto.hash for XOF functions #58121 gets on track

After this lands a semver-major PRs that contain breaking changes and should be released in the next major version. will follow with a runtime deprecation.

This will need backporting all the way back to 20.x

Reverts: #56160
Fixes: #56159
Fixes: #58913
Refs: #58121

Note: FWIW #56160 should not have landed. Any OpenSSL version-related test changes should only accomodate changes in codes, not behaviour.