fix(security): verifier contract range limit checks

[skarred14]

Description

Following an issue raised by @weijiekoh this PR checks for the range limits for proof and public inputs to the verify() in Verifier.sol. Although there are parameter in the radish34/api/src/utils/crypto/ecc/babyjubjubparams.js that are utilized in signature verification, there is currently no additional check against the inputs that any user could enter while interacting directly with the deployed Verifier contract

Related Issue

#34

Motivation and Context

Test data for the Verifier.test.js is based on running/debugging the integration test

semaphore-protocol/semaphore#16
https://github.com/appliedzkp/semaphore/blob/master/contracts/sol/verifier.sol#L199

How Has This Been Tested

All tests at the root level as indicated in npm run test pass. New tests at radish34/contracts/ level also pass.

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[brian-lc]

Thanks for the fix! Glad to see the boundary checking in place. Could you add some tests to make sure we don't loose this in some refactoring/regression?

[skarred14]

test cases updated

[bitwiseguy]

All tests pass for me