[Spike] Service Date Range timezone format

[Alessandro100]

Describe the problem

If we look at a validation report example we see the Feed Start Date / Feed End Date formatted as such 2014-10-18. This could cause inaccuracies when working with countries that have different timezones "Japan vs Canada"

Proposed solution

Spike objectives
[] present a way to store Feed Start Date / Feed End Date which includes timezones
[] present a way to compare if the current time is inside the service window. Needed to set the status of the feed
[] present a way to get the timezone from the validation report where there is currently none (by country code?)

Alternatives you've considered

No response

Additional context

No response

[Alessandro100]

Spike conclusion: We will store the service date range without timezones

Reasoning
Including timezones in the service date would avoid errors in status in a range of +- 12 hours. Since the status is going to be updated daily, there will already be an error range of 23 hours, no use in optimizing for timezones which introduces complexity.

Follow up ticket (future)

• extract the timezone from agency.txt and save that in datasets