[BUG] Date Formats flipped for most fields

[Prajna1999]

According to OCDS specifications, all dates should be formatted as YYYY-MM-DDT00:00:00Z.

In the current version of public facing data all dates should be already formatted like this, but that was not addressed in the main data transformation script, but rather in additional bash scripts. Prior to next release we need to ensure that all dates are formatted correctly in the main data transformation script.

Currently there are a couple of different formats in use (examples provided not from public facing data, but from the draft data)

date: 2023-10-19
tendrer/datePublished: 2017-29-04 12:00
tender/tenderPeriod/startDate: 2017-29-04 12:00
tender/tenderPeriod/endDate: 2017-29-05 14:00
tender/communication/documentAvailabilityPeriod/startDate: 2017-30-04 12:00
tender/communication/documentAvailabilityPeriod/endDate: 2017-29-05 14:00
tender/bidOpening/date: 2017-29-05 14:00
tender/enquirePeriod/startDate: 2017-13-06 14:00
tender/enquirePeriod/endDate 2017-16-06 12:00
tender/milestones/dueDate: 2017-20-04 14:00
tender/amendments/date: 2018-18-06 16:05
bids/details/date: 2017-20-04 13:53
awards/contractPeriod/startDate: I don't have the latest format here, but probably it is the same as the most dates

As you can see, in most of this cases, date and month parts of the date object are swapped, so that's an additional issues that should be addressed during the formatting.

If there's need we can also document how date looks like in the source (scraped) data. That might provide better understanding of how this issue can be addressed.

[Prajna1999]

@AakashGandhi1 for now write a simple python/bash script to fix the thing and refactor/rewrite into the new repo