Update VEText Forwarder Lambda Logging

[k-macmillan]

User Story - Business Need

Update the logging in the vetext forwarder lambda to be in-line with our logging policy.

• [ ] Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)

As a VA Notify Engineer I want to log in accordance with our policies So that we are consistent across the platform

Additional Info and Resources

• logging policy

Engineering Checklist

• [ ] All logging includes string qualifiers (nothing like logger.info(event))
• [ ] Proper use of info, warning, and error/critical
• [ ] MessageSid is recorded in the logs
• [ ] MessagingServiceSid is recorded in the logs
• [ ] To (the service's phone number) is recorded in the logs
• [ ] From and other identifying fields are not recorded outside of debug or error/critical logging

Acceptance Criteria

• [ ] Code not related to logging is not changed at all
• [ ] Logging output coincides with the logging policy

QA Considerations

Logging has no opportunity for new errors

[mjones-oddball]

Hey team! Please add your planning poker estimate with Zenhub @babyjunior56 @cris-oddball @EvanParish @k-macmillan @kalbfled @ldraney @nikolai-efimov