#1497 Update logging for the Vetext forwarder lambda

[kalbfled]

Description

These changes update logging for the Vetext forwarder lambda to bring it into compliance with our logging document. Note that using logger.exception logs at the "Error" level and includes the stack trace in the output.

issue #1497

How Has This Been Tested?

I deployed the branch with lambdas and let the regressions run.

Checklist

• I have assigned myself to this PR
• PR has an appropriate title: #9999 - What the thing does
• PR has a detailed description, including links to specific documentation
• I have added the appropriate labels to the PR.
• I did not remove any parts of the template, such as checkboxes even if they are not used
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to any documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works. Testing guidelines
• I have ensured the latest main is merged into my branch and all checks are green prior to review
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• The ticket was moved into the DEV test column when I began testing this change

[k-macmillan]

Returning 403 on unauthenticated Twilio request for event should be a warning.
We should log the unsuccessful request responses from VEText in the make_vetext_request method.
Unable to encrypt/json dump error logging should be exception.