feat: enforce max 10 OTP requests for verified field

[mantariksh]

Problem

There is no limit to the number of OTPs users can request for a given transaction ID. This allows users to continually request for OTPs, which can be costly in the case of SMSes.

Solution

Enforce a limit of maximum 10 OTPs before user needs to refresh.

Breaking Changes

• No - this PR is backwards compatible

Screenshots

Tests

• Requesting OTP for the 11th time results in the error seen in above screenshot
• Refreshing page clears error, allowing user to verify the field
• Entering a wrong OTP results in hashRetries incrementing but not otpRequests
• Requesting for a new OTP results in otpRequests incrementing and hashRetries being reset to 0
• Request an OTP on the old server, then switch over to the new server. Requesting another OTP results in the otpRequests key being added to the field object in the database, with a value of 1.

[karrui]

lgtm wah anti writing code again how does this feel

[hanstirtaputra]

LGTM