🐛 Fix types in `pbkdf2`

[boorad]

What's happening?

The tests for pbkdf2 are littered with as number or as HashAlgorithm. Investigate if we have deviated from the Node API.

Reproducible Code

crypto.pbkdf2(
      // @ts-ignore
      passphrase,
      salt,
      iterations,
      keylen,
      digest,
      (err, derived) => {
        if (err) {
          reject(err);
        } else {
          //@ts-ignore
          resolve(derived);
        }
      }
    );

Relevant log output

n/a

Device

sim

QuickCrypto Version

1.0.0-beta.11

Can you reproduce this issue in the QuickCrypto Example app?

Yes, I can reproduce the same issue in the Example app here

Additional information

• I am using Expo
• I have read the Troubleshooting Guide
• I agree to follow this project's Code of Conduct
• I searched for similar issues in this repository and found none.

[boorad]

Fixed in 6e373ec. The pbkdf2() and pbkdf2Sync() digest parameter now accepts string (matching Node.js API). The normalizeHashName helper validates at runtime and throws for unsupported algorithms. Also cleaned up the test/benchmark casts and split the fixture types.