housekeeping: use 88 bit range checks for `Field.parity`

[mitschabaude]

This should be expanded to be "expose primitives for efficient range checks to snarkyjs and use them everywhere possible".

Things that are super expensive and we can speed up with range checks:

• Field comparisons (they use naive full bit decomposition)
• Field parity - also used implicitly when (de)compressing public keys, i.e. in privateKey.toPublicKey()
• all UInt32 / UInt64 operations (they already use more-efficient-than-naive range checks but could still be much more efficient)