fix(crypto): correct compareTo checks in BigInteger RNG helpers

[Kr0emer]

Summary

This PR fixes incorrect compareTo handling in BigInteger rejection sampling utilities used by DSA nonce generation.

Root Cause

BigInteger.compareTo may return any positive/negative integer, but code assumed sentinel values (-1/1), causing:

• possible acceptance of out-of-range random candidates in getRandomBigIntegerZeroToMax
• fragile min/max guard in getRandomBigIntegerMinToMax

Fix

• src/crypto-1.1.js
  • biMax.compareTo(biRand) != -1 -> biMax.compareTo(biRand) >= 0
  • flagCompare == 1 -> flagCompare > 0

Tests

Added regressions in test/qunit-do-crypto.html:

• reject out-of-range candidate and retry in getRandomBigIntegerZeroToMax
• throw for any positive compareTo result in getRandomBigIntegerMinToMax

Validation

• Targeted fix checks passed (rejection-sampling and min/max guard behavior).
• DSA-path telemetry check (1000 signatures) showed overflow = 0.
• Full npm test may depend on local network/installed dependencies.