crypto: variable-length hash algorithms do not throw errors for non-integer/non-safe-integer lengths, tests cases assume they do, but test logic is broken and suppresses the assertion failures

[jeremyBanks]

@quentinadam and @iuioiua noticed in #3793 (comment) that the crypto_test.ts logic was failing to check that errors were being thrown when expected.

I've made a commit that fixes the test logic: jeremyBanks@e571f76. Upon fixing it, three tests start to fail for two cases each: the three variable-length hash algorithms, BLAKE3, SHAKE128, and SHAKE256 do not throw errors for the cases Non-integer length with options {"length":1.5}) (which they treat as length: 1) and Too-large length with options {"length":8.112963841460666e+31}) (which they treat as length: 0), but our current test cases expect them to throw errrors.

The test logic definitely needs to be fixed, so that commit should be applied, but obviously that can't be merged until we also fix the crypto.ts logic to perform the expected checks (which might be considered BREAKING if we're being super-pedantic, but is probably safe in practice), or to change the expected result.

Some might argue that that truncating 1.5 to 1 is okay (I would prefer it to be an error), but I think all would agree that any length that's too large to fit into 32 bits (usize for WASM targets) should throw an error instead of being truncated to 0.