SMS rate limiting requests/feedback

for context we have a native mobile app that uses SMS OTP for authentication exclusively. we saw a spike in signups and quickly hit the SMS rate limiting this morning (which I only discovered after finding [this PR]( this raised a few quick points of feedback: 1) default should be more than 30/hour. totally just our perspective, but that seemed shockingly low to us. I realize that the rate limit is probably in place for spam, but we have spend management well handled on the Twilio side so additional throttling feels a little unnecessary/restrictive, and the risk of declining good users seems very high. 2) logs for SMS OTP rate limiting show up as info statements instead of errors. not sure if this intended (in which case I just found it very unintuitive!) or a bug. this definitely slowed down our ability to identify the issue. <img width="533" alt="Screen Shot 2023-05-10 at 8 50 16 AM" src=" 3) while it's great to see of requests, for repor…