#2159 - Update Total Time For Twilio Delivery Status

[k-macmillan]

Description

Twilio delivery status can come in with a negative timestamp due to only having minute granularity. This only affects our logging but has been updated so our internal charts and logs are not confusing.

issue #2159

How Has This Been Tested?

Wrote a new test. Deployed.
Ran requests using Twilio at various times to attempt to trigger a negative number, all were positive:

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

[kalbfled]

This is fine. You could also have log_notification_total_time return the time to facilitate testing.