Expand crypto parity coverage

[TheHypnoo]

Summary

Expands Perry's node:crypto parity coverage with a broad deterministic test suite curated from Node.js, Bun, and Deno crypto compatibility coverage, and closes the compatibility gaps discovered while porting those cases.

This PR adds granular TypeScript parity tests for the main crypto surfaces and documents the intentionally deferred gaps in test-parity/node-suite/crypto/README.md.

Covered areas

• Module import shapes, inventory helpers, constants, FIPS/secure heap API shape, and function/method name parity.
• Hash/HMAC coverage including algorithm aliases, encodings, buffer output, XOF output length, update input encodings, digest reuse, crypto.hash(), and legacy callable constructors.
• PBKDF2, HKDF, scrypt, random bytes/fill/int/UUID, prime generation/checking, and timing-safe equality.
• AES-CBC/ECB/GCM/KW coverage including auto-padding, AAD options, auth tags, SecretKey input, and getCipherInfo().
• RSA/RSA-PSS sign/verify/encrypt/decrypt, EC P-256, DH/ECDH/X25519, key generation, KeyObject/JWK coverage, and async callback APIs.
• WebCrypto coverage for digest, HMAC, AES-CBC/CTR/GCM/KW, ECDSA/ECDH P-256, Ed25519, X25519, RSA-OAEP/RSA-PSS/RSASSA, JWK import/export, deriveBits/deriveKey, and wrap/unwrap.

Runtime/codegen changes

• Extends node:crypto native support for the parity suite areas above.
• Adds handle property dispatch for crypto method-as-value reads.
• Adds SecretKey, KeyObject, cipher, WebCrypto, asymmetric, random, and async callback compatibility behavior needed by the new tests.
• Propagates Hash.update() / Hmac.update() input encodings through the codegen fallback path.

Validation

Latest local run:

find test-parity/node-suite/crypto -type d -name .perry-cache -prune -exec rm -rf {} + && ./run_parity_tests.sh --suite node-suite --module crypto

Parity Pass:   181
Parity Fail:   0
Compile Fail:  0
Skipped:       0
Parity Rate:   100.0%

Report generated locally at:

test-parity/reports/parity_report_20260522_200142.json

Known follow-up gaps

These are intentionally left for future PRs:

• X509Certificate and crypto.Certificate / SPKAC APIs.
• Full Node stream-backed crypto transform semantics.
• Exact DER/PEM encrypted key import/export variants and OpenSSL-specific error codes.
• WebCrypto P-384/P-521, Ed448/X448, AES-OCB, ChaCha20-Poly1305, PQC/KMAC/Argon2 surfaces.
• AES-GCM 4-byte and 8-byte auth tags; the current RustCrypto backend supports the 12-16 byte tag sizes covered here.
• Exact CryptoKey/KeyObject.toCryptoKey() asymmetric object identity/prototype behavior.
• Large-prime/BigInt prime generation parity beyond the practical deterministic coverage in this suite.

[TheHypnoo]

Note on CI flake: the cargo-test job is intermittently failing with signal: 11, SIGSEGV: invalid memory reference in the perry-runtime test binary, on the same test binary hash (perry_runtime-cdd58eada73e5edc) that other unrelated PRs hit at the same time. Sample affected PRs:

• fix/perf-measure-missing-mark-1403 (commit 1e11ff75) — failed at 21:14
• feat/fs-parity-expansion (commit 89036aad) — failed at 21:10
• feat/crypto-parity-expansion (this PR) — failed at 20:51, 20:30

Other PRs that ran in between (fix/perf-observer-no-cb-1388, fix/perf-resource-timing-1339, fix/perf-tojson-1338) passed cleanly. No GC files changed in this PR vs main (git diff origin/main..HEAD -- crates/perry-runtime/src/gc/ is empty), so the SIGSEGV is not introduced by these changes. Local reproduction shows multiple gc::tests::oldgen::* tests deadlocking on a shared Mutex, consistent with a recently-introduced parallel-test ordering issue rather than memory corruption.

Will retry the Tests workflow once if it fails again on the latest push (commit ca761af9).