Consider removing times from the start dates and ends dates in the Schedule JSON files

[chriswmackey]

From what I have been able to tell, the schedules in the standards gem ultimately map to ScheduleRulesets in the OpenStudio SDK and each of the lists of schedule values in the JSON map to ScheduleRules (correct me if I am wrong).

If this is true, then I see that the OpenStudio SDK only cares about the month and the day and not anything else related to the date like the year, hour, minute, or second. The start_date and end_date values in the Schedules JSON therefore have all of this extra info that isn't used and ends up being a bit misleading for people trying to make use of the data in the JSONS:

I realize that this isn't really a bug but it seems like something that could be addressed relatively easily in the way the schedule JSONS are exported from the google sheets and this would go a long way to making the logic of the JSONs more understandable for those people making use of them.

[mdahlhausen]

I agree that the hour/minute/seconds are not necessary here.

This is an artifact of using DateTime.parse instead of Date.parse in Ruby.

      start_date = DateTime.parse(rule['start_date'])
      end_date = DateTime.parse(rule['end_date'])

It seems that Date.parse would work just as well here since we are only using the month/day/year. @asparke2 is there any reason to keep the hour:minute:second values in the .json files? They aren't in the spreadsheet.