crypto: support ML-DSA KeyObject, sign, and verify

[panva]

This allows node:crypto to recognize the following asymmetric KeyObject types (keyObject.asymmetricKeyType) when built with or linked to OpenSSL 3.5 (#59234):

• 'ml-dsa-44', 'ml-dsa-65', 'ml-dsa-87' (https://docs.openssl.org/3.5/man7/EVP_PKEY-ML-DSA/)
• key fixtures and makefile targets to re-generate them

And the following functionality for them:

• import crypto.createPublicKey() SPKI/JWK
• import crypto.createPrivateKey() PKCS#8/JWK
• export keyObject.export() SPKI/PKCS#8/JWK
• keygen crypto.generateKeyPair(Sync)() into KeyObject, PEM, DER, JWK
• ML-DSA signing via crypto.sign() and signature verification via crypto.verify()

---

notable-change PRs with changes that should be highlighted in changelogs.

ML-DSA support in node:crypto kicks off post-quantum cryptography efforts in Node.js. This is part of a broader effort to support NIST's post-quantum cryptography standards for future-proofing applications against quantum computing threats.

---

TODO:

• JWK format support in crypto.createPublicKey() and crypto.createPrivateKey()
• check if we can set ML-DSA's optional context-string as an option from crypto.sign() and crypto.verify()
  • yeah, maybe in a followup PR.

[nodejs-github-bot]

Review requested:

• @nodejs/crypto
• @nodejs/gyp
• @nodejs/security-wg

[panva]

cc @nodejs/cpp-reviewers 🙏

[github-actions]

The notable-change PRs with changes that should be highlighted in changelogs. label has been added by @panva.

Please suggest a text for the release notes if you'd like to include a more detailed summary, then proceed to update the PR description with the text or a link to the notable change suggested text comment. Otherwise, the commit will be placed in the Other Notable Changes section.

[codecov]

Codecov Report

❌ Patch coverage is 78.76712% with 31 lines in your changes missing coverage. Please review.
✅ Project coverage is 89.98%. Comparing base (5335c10) to head (7b10239).
⚠️ Report is 21 commits behind head on main.

Files with missing lines	Patch %	Lines
src/crypto/crypto_keys.cc	73.80%	3 Missing and 8 partials ⚠️
src/crypto/crypto_ml_dsa.cc	73.68%	2 Missing and 8 partials ⚠️
lib/internal/crypto/keys.js	82.97%	8 Missing ⚠️
lib/internal/crypto/keygen.js	89.47%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #59259      +/-   ##
==========================================
+ Coverage   89.97%   89.98%   +0.01%     
==========================================
  Files         649      650       +1     
  Lines      192131   192321     +190     
  Branches    37653    37722      +69     
==========================================
+ Hits       172864   173056     +192     
+ Misses      11883    11840      -43     
- Partials     7384     7425      +41     

Files with missing lines	Coverage Δ
src/crypto/crypto_keys.h	56.60% <ø> (ø)
lib/internal/crypto/keygen.js	91.93% <89.47%> (-0.67%)	⬇️
lib/internal/crypto/keys.js	94.81% <82.97%> (-0.60%)	⬇️
src/crypto/crypto_ml_dsa.cc	73.68% <73.68%> (ø)
src/crypto/crypto_keys.cc	72.31% <73.80%> (-0.40%)	⬇️

... and 54 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jasnell]

Not a blocker but, does this also need to have a OPENSSL_IS_BORING guard? I doubt boring would end up duplicating these version values but just want to be cautious.

/cc @codebytere

[jasnell]

first view pass looks good but there's a lot here so I want to take a second pass through before signing off.

[nodejs-github-bot]

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