I0617 rescu sensors eval

[gabrielwol]

What this pull request accomplishes:

• Identify RESCU detectors to repair this year during annual repair blitz.
• SQL to identify network wide outages and individual sensor outages.

Issue(s) this solves:

• #617

What, in particular, needs to reviewed:

volumes/rescu/Data validation/identify_sensors_to_repair_i0617.sql - create a list of detectors classified as good/bad/inactive to map for geographic distribution. volumes/rescu/Data validation/identify_detectors_for_repair.png - visual output from above sql used to determine sensors to repair. volumes/rescu/create-view-network-outages.sql - identify network wide outages (no values from any sensor over any duration). Necessary because we don't want to count network wide outages against individual sensors. volumes/rescu/create-mat-view-individual-outages.sql - identify individual detector outages (exlude overlapping portions from network wide outages). Could be useful for future data requests.

What needs to be done by a sysadmin after this PR is merged

Should we migrate these tables to rescu schema? E.g.: these tables need to be migrated/created in the production schema.

[radumas]

can you rename the Data Validation folder to validation? The fluffer doesn't like the space, and I am allergic to capitalization.

[radumas]

So we're going to revisit this and find the work a new home within the new volumes/vds folder after https://github.com/CityofToronto/bdit_data-sources/pull/646 gets merged

[radumas]

Realize this wasn't introduced in this PR but the below bullets didn't render properly

https://github.com/CityofToronto/bdit_data-sources/blob/404501559b3fb7ba9db3e3c9814223ec4706a649/volumes/vds/readme.md?plain=1#L146-L148