Fix timezone issue on csv import #2820
Description
Describe the task
The date times imported from the csv are off, likely due to timezone assumptions by the database. The csv import needs to be re-run with a fix applied so the dates in ALCS are consistent with the dates in the csv
Determine if it makes sense to bring the csv import code into the ETL, knowing that we need to make this fix and that more might come up in the future. And we need to do the import again with the actual production data when it comes time to cut over.
Acceptance Criteria
- determine if we should bring import code into ETL
- fix csv import code to correctly handle timezones -> example: 55979 (csv "Date" is June 1, 2017; alcs "date_submitted" is May 31, 2017)
Changed the format on the 'Date' field from 'date' to 'datetimezone':
https://bcgov-my.sharepoint.com/:x:/r/personal/ansley_charbonneau_gov_bc_ca/Documents/ALCS%20Development/FY25-26/C%20and%20E/2026%2001%2019%20Complaint%20data%20for%20nris%20schema%20incl.%20No%20Action,%20updated%20to%20datetimezone.xlsx?d=w4c3364beaf2946119b2ae4a0a6a3884d&csf=1&web=1&e=X8cnVW