OpenSSL 3 provider implementations are not necessarily registered in the legacy digest and cipher tables used by EVP_get_digestbyname() and EVP_get_cipherbyname(). As a result, Node.js can omit usable provider-only algorithms from getHashes() and getCiphers() and reject them in crypto operations even when they match the active OpenSSL property query. The permanently memoized algorithm lists can also remain stale after setFips() changes that query.

This change discovers usable hashes, ciphers, and aliases from activated OpenSSL providers while preserving the legacy registries. Numeric OID aliases, NULL implementations, and cipher implementations unsupported by the Node.js Cipher APIs are excluded.

Resolution and API support

• Provider digest resolution now covers streaming and one-shot hashing, HMAC, KDFs, signing, verification, and RSA digest options.
• Provider cipher resolution is used for string-based initialization and getCipherInfo() while preserving numeric, WebCrypto, TLS, and predefined-cipher paths.
• Provider discovery exposes algorithms including KECCAK-KMAC-128, KECCAK-256, SHA256-192, CBC-CTS variants, SM4-GCM, SM4-CCM, SM4-XTS, and additional AES key-wrap implementations when supplied by the active providers.
• createHash() and crypto.hash() accept functionName and customization for cSHAKE digests with OpenSSL 4.0 or later.
• Cipher construction accepts ctsMode for CBC-CTS and xtsStandard for selecting the provider XTS variant.
• CBC-CTS, AES key wrap, SIV/GCM-SIV, and CCM decryption enforce the one-shot and authentication constraints required by their provider implementations.

Caching and invalidation

• Ordinary hashes and ciphers retain their legacy lookup and direct initialization paths, and the extended native binding arities are used only when the new cSHAKE, CTS, or XTS options are supplied.
• Successful provider fetches are cached per Environment under case-insensitive query, canonical, and alias names, with owners deduplicated by provider and canonical identity.
• Warm cache hits return borrowed pointers without another explicit fetch or reference increment, and failed lookups are not cached.
• A process-wide generation advances only after a successful setFips() call that changes the FIPS state.
• Each Environment lazily clears aliases before releasing owning provider references when it observes a new generation.
• getHashes() and getCiphers() keep independent generation-aware snapshots, retry enumeration if the generation changes concurrently, return defensive copies, and discard their JavaScript snapshots during snapshot serialization.
• Existing hash and cipher contexts retain their implementation and can finish across a FIPS transition, while new contexts resolve against the new property query.
• Provider owners are released before worker addon DSOs are unloaded.
• Engine registration changes, explicit provider load or unload, and default-property changes made by native addons intentionally do not participate in this invalidation mechanism since engines are on the way out of the codebase (crypto,https,tls: runtime-deprecate OpenSSL engine-based APIs (DEP0183) #63966, crypto,build: require OpenSSL 3, drop the bundled FIPS provider build #64777 (comment)).

Fixes: #43040
Fixes: #64866
Refs: #62982