Build UX/UI for data export

[nathanielrindlaub]

I've wired up a simple button that triggers a CSV export and stores a pre-signed URL for the CSV in S3, so next steps are:

• [x] automatically open the URL to download the CSV
• [x] A modal component for data exporting (a place where users can choose between COCO CameraTraps or CSV export, read disclaimers on how they work, and we can display warnings like "56 of the 593 images you exported were not reviewed, so they were not included")
• [x] add tool-tips on hover on the filter panel footer buttons
• [x] improve error handling/messages

[nathanielrindlaub]

This is implemented, but we're running into timeout issues when you try to export all of SCI's data (>80k images). I think I'll try to create & update status documents in S3 for each export job, which the front end can poll until the status changes to "success", and then allow it to be downloaded via the presigned URL.

See same approach in shp2json and kelpwatch:

• managing the status document in s3: https://github.com/tnc-ca-geo/shp2json/blob/main/transform/index.js
• API routes for checking the status document: https://github.com/tnc-ca-geo/shp2json/blob/main/api/routes/upload.js
• Kelpwatch integration: https://github.com/tnc-ca-geo/kelpwatch/blob/v2_release/frontend/kelpwatch/src/state/map/middleware.js#L99

[nathanielrindlaub]

Successfully implemented the approach above. Moving on to some clean up & polish:

• [x] FIX modal bug!!!
• [x] follow MDN guidance on best practices for window.open() - popups and redirects can be blocked, so add link to export modal when the url is ready
• [x] add some text about the export potentially taking a long time in modal
• [x] polish export modal styling
• [x] rethink shape of csvExport in state, make sure I’m happy with it
• [x] poll every 2 seconds
• [x] handle errors from getExportStatus document

[nathanielrindlaub]

Done