feat: sms limiting

[seaerchin]

Problem

This PR adds sms limiting!

This PR comprises of a few sections:

1. email sending (warning/disabled)
2. admin facing frontend (conditional modal showing depending on whether admin has exceeded limit)
3. backend changes (pre-save hook on smscounts; checking whether to send email or not; checking whether we should disable the admin's ability to send sms)

More relevant information can be found in the individual PRs!

This PR has 2 unreviewed commits here and here which does 2 things. It removes the smsVerificationLimit env var and removes unused typings.

Closes #1935

Solution

see individual PR

Breaking Changes

• Yes - this PR contains breaking changes
  • This PR updates the FE to call a new API and has a new UI

Manual Tests

Happy path without db access

• Create 2 new forms with a mobile field and sms verifications enabled
• On 1 form, request to verify your phone number.
• Return to the form and attempt to add a new mobile number field. The count should be updated
• Attempt to edit the other mobile number field. The count should also be updated.
• Go to the other form, and repeat the above 2 tests.

Warning email tests - requires db migration

• Create 2 forms with verifiable mobile fields. ensure that 1 of them has the msgSrvcName property set.
• Create a form with a verifiable mobile field. Insert 2499 smses into the db (see the misc section down below).
• Open the form and subsequently, the mobile field. Verify that the counts has been updated.
• request for otp verification. Should receive an email warning form admin about the limit. Attempt to toggle the mobile field on again - this should succeed and show the updated count.
• Verify that there is a warning email receieved.
• Ensure that the email received has 2 form titles. (the 2 forms w/o msgSrvcName)
• Ensure that the form with msgSrvcName is not shown in the email
• Repeat the above steps for 4999/7499 smses and verify the result

Disabled email tests - requires db access

Have the edit mobile field window open before proceeeding. Toggle on the sms verification feature and do not save. Remain on the modal. Create another form in the staging db and set a msgSrvcName so that it acts as an onboarded form

• Have a window/tab with the form open prior to inserting smses.
• Insert 10k smses. attempt to verify with the tab/window from previously. this should succeed. next, refresh the public forms page/navigate back (now the form has >10k smses). the verify option should not be there.
• Now attempt to save the edit mobile field modal as an admin (with otp verification toggled on). There should be a toast informing you that the update is invalid.
• Attempt to duplicate the mobile field. This should work. Click on the mobile field. It should be disabled.
• Attempt to duplicate this form. This should work. Verify that the duplicated form also has sms verification disabled.
• Attempt to use the form as a template. This should work. Verify that the duplicated form also has sms verification disabled.
• Close the edit mobile field modal and reopen it. Verify that the toggle is greyed out.
• Verify that you have received an email warning you that your forms have sms verifications disabled.
• Transfer the form to ${name}+1@${domain here} and make them the owner. Open the form and verify that sms counts have been reset.
• Ensure that the other form with msgSrvcName is not affected and mobile number field can still be toggled

Misc

db script to insert sms counts into staging db:

/*
Populates the database with the given number of sms in the sms_counts collection
*/

// == PRE-UPDATE CHECKS ==
const formId = ObjectId('insert credentials here')
const formAdminId = ObjectId('insert credentials here')
const formAdminEmail = 'insert credentials here'
const msgSrvcSid = 'insert credentials here'
const numberToCreate = 2500
// A: Retrieve smscounts of the user before updating
db.getCollection('smscounts').countDocuments({
  'formAdmin.userId': formAdminId,
  smsType: 'VERIFICATION',
  isOnboardedAccount: false,
})

// == UPDATE ==
// B: Insert smscount document into smscounts collection
const documentsToCreate = Array(numberToCreate).fill({
  smsType: 'VERIFICATION',
  form: formId,
  formAdmin: {
    email: formAdminEmail,
    userId: formAdminId,
  },
  msgSrvcSid,
  logType: 'SUCCESS',
  createdAt: ISODate('2021-06-30T07:41:53.768Z'),
  isOnboardedAccount: false,
  __v: 0,
})
db.getCollection('smscounts').insertMany(documentsToCreate)

// == POST-UPDATE CHECKS ==
// Check smscounts of the user after updating
// Should be equivalent to A + B
db.getCollection('smscounts').countDocuments({
  'formAdmin.userId': formAdminId,
  smsType: 'VERIFICATION',
  isOnboardedAccount: false,
})

[seaerchin]

i can rebase to remove #2276 and #2250 since both of em will be merged into develop

[karrui]

lgtm, reviewed last two commits only