crypto: ensure CryptoKey usages and algorithm are cached objects

[panva]

As per the spec both the usages and algorithm are "cached", i.e. not new objects every time the getter is invoked.

This fixes the behaviour for usages and adds tests for both.

[nodejs-github-bot]

Review requested:

• @nodejs/crypto

[panva]

• WPT for algorithm was added in Return cached object from CryptoKey.algorithm getter web-platform-tests/wpt#48923
• WPT for usages was added in [WebCryptoAPI] test cached usages slot as well web-platform-tests/wpt#49453

[panva]

cc @nodejs/web-standards

[nodejs-github-bot]

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.00%. Comparing base (08e0147) to head (e05035c).
Report is 20 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #56108      +/-   ##
==========================================
+ Coverage   87.96%   88.00%   +0.03%     
==========================================
  Files         656      656              
  Lines      188383   188981     +598     
  Branches    35975    35993      +18     
==========================================
+ Hits       165716   166308     +592     
+ Misses      15842    15832      -10     
- Partials     6825     6841      +16     

Files with missing lines	Coverage Δ
lib/internal/crypto/keys.js	93.88% <100.00%> (-0.01%)	⬇️

... and 39 files with indirect coverage changes

[nodejs-github-bot]

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

[nodejs-github-bot]

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