Changes to Support RideNoCo TDS

[NomeQ]

This should possibly get broken into sub-issues. I propose this serves as a complete list of items, and anything that is larger/more involved can become its own issue (and be linked here). Intention is for these to be the changes that must be done for the mid-january due date (Jan 22nd vendor meeting).

P1 Support TripRequest telegram 1A

• [x] Update HMAC to follow spec (on Swagger)
• [ ] Update TripRequest logic in ordering client - Send TripRequest - POST
• [ ] Update TripRequest logic in provider - API receives POST request - sends expected response telegram - uses new error codes/messages
• [ ] Change Date/Time formatting to match new spec
• [ ] Use GUIDs where agreed upon - tripTicketId, customerId (?)
• [ ] Update address formatting throughout
• [ ] Support all required fields
• [ ] Move customerInfo into TripRequest telegram

[NomeQ]

• For sharing - consider breaking out shared API into its own sheet
• UUID library already in apps script (example in trips line 17)
• plus code support??? think about it (but maybe don't implement now)