Server should use GoodCFVerify to send sms verification

[sirpy]

Modify server to send SMS via worker and not directly using twilio so the logic for 3rd + 4th request is the same

on server

• [x] add env variable with jwt password for the worker
• [x] on sendOTP request send {to, verify:true} signed object to worker
• [ ] on checkOTP seend {to,code, verify:true} signed object to worker

on worker

• [x] separate request handling based on "verify" param. which is true for incoming requests from our backend
• [x] if code param doesnt exists in request then perform verify request to twilio with server VerifyID just like we do for auth0 with same state logic
  • [ ] with the diffeerence that we dont send a custom code
• [ ] if code param exists in request perform verification check request to twilio with server VerifyID
• [x] pipe twilio API response directly back to backend (ie no processing at all on worker like we do for auth0) see:https://developers.cloudflare.com/workers/learning/using-streams

[omerzam]

@sirpy since I don't have a custom code when coming from the server using the programmable SMS is impossible I will add logic to skip this step when coming from the server and going straight to voice verification

[omerzam]

after consulting with @sirpy : generate the code in the worker and keep it in the KV store

[iLystopad]

@sirpy The user gets the verification code by SMS without issues (except #2939) after editing the Phone number on the Edit profile screen and after sign in/up with Auth0/Google/Facebook.

Checked on the QA 1.24.1-6 Device: Desktop / Windows 10 / Google Chrome 89.0.4389.90