[BUG] Fractional seconds misinterpreted for date ranges

[elavy-harris]

Describe the bug
If an API call specifies more than 3 digits for fractional seconds, the value is interpreted incorrectly.

To Reproduce
Steps to reproduce the behavior:

1. Find the oldest message for any channel (assuming that it has not been reprocessed using the "overwrite existing messages and update statistics" checkbox)
2. Note the "received date"
3. Run a curl command like the following: curl -ksu elavy -X GET "https://localhost:18443/api/channels/d04e8e83-93d1-4559-83d6-50216613cb24/messages?endDate=2023-01-10T22%3A20%3A29.999000%2B0000&limit=20" -H "accept: application/xml" -H "X-Requested-With: OpenAPI" . Replace endDate with a time 1 second before the actual received date. KEEP the 999000.

Expected behavior
No messages returned

Actual behavior
Messages returned for about 16.6 minutes beyond the specified time.

Environment (please complete the following information):

• Docker image nextgenhealthcare/connect:4.5.0
• Connect Version 4.5.0

Workaround(s)
Always specify 3 digits for fractional seconds.