fix: clamp smi in fast calls by default

[littledivy]

Fixes #26480

Ref denoland/deno_core@d2945fb

[nathanwhit]

That fixes the panic but randomInt is still incorrect, the user could be wanting an int in the range 0 to Number.MAX_SAFE_INTEGER but we would clamp that and only return a value up to 2^31-1.

I think instead we should take a number (i64 probably) in the op. If it hurts perf, I guess you could have two ops (one smi) and choose based on the bounds.

[jerome-benoit]

That fixes the panic but randomInt is still incorrect, the user could be wanting an int in the range 0 to Number.MAX_SAFE_INTEGER but we would clamp that and only return a value up to 2^31-1.

The input range supported by randomInt() is not [0, Number.MAX_SAFE_INTEGER] but [0, 281474976710655]. In case (max - min) > 281474976710655, a RangeError is thrown.

[nathanwhit]

LGTM