feat: Improved compliance of crypto object

[nabetti1720]

Description of changes

Add the following methods to improve the compliance of crypto Object.

• crypto.getRandomValues()

Checklist

• [x] Created unit tests in tests/unit and/or in Rust for my feature if needed
• [x] Ran make fix to format JS and apply Clippy auto fixes
• [x] Made sure my code didn't add any additional warnings: make check
• [x] Updated documentation if needed (API.md/README.md/Other)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[nabetti1720]

I might be wrong but I think it’s the view (the type array) that determines how the underlying array buffer is behaving. So it’s always a u8 array of numbers but viewed as a for example Float64Array those u8s would represent 64 bit floats instead. But it might overflow for floats in IEEE format

For this very reason, the specification does not seem to support Float32Array and Float64Array. That is to say, it may appear to be an incorrect value when viewed as a Float32Array or Float64Array.

ChatGPT seemed to know this and suggested a workaround in Javascript. :) This code also works with the current LLRT.

function getRandomFloat32Array(length) {
    var buffer = new ArrayBuffer(length * Float32Array.BYTES_PER_ELEMENT);
    var floatArray = new Float32Array(buffer);

    var uintArray = new Uint32Array(buffer);
    crypto.getRandomValues(uintArray);

    for (var i = 0; i < length; i++) {
        // Convert 32-bit unsigned integer to float between 0 and 1
        floatArray[i] = uintArray[i] / (0xFFFFFFFF + 1);
    }

    return floatArray;
}

// Example usage
var floatArray = getRandomFloat32Array(10);
console.log(floatArray);

Since we cannot find a good solution at this time, we would like to exclude Float32Array and Float64Array from support.

https://developer.mozilla.org/en-US/docs/Web/API/Crypto/getRandomValues As indicated previously, this is because support for these two Arrays is not a requirement.

I am sorry for not being able to help you.

[richarddavison]

I think we can go ahead and simply exclude support for float typed arrays

[nabetti1720]

Thank you for your consideration. It has already been completed in the last commit.