Innovation: Get Peak Burniness 2.0 in a state ready for production

There's a number of steps necessary before Peak Burniness 2.0 can be turned into an actual product in production:

- [ ] set up IDIR authentication on front-end (all the weather data from BCFW Phase 1 is behind idir protection, so presumably we need to continue doing the same)
- [ ] set up object storage and migrate all source data files into our store
- [ ] write unit tests to ensure that scripts for data analysis have been written correctly (e.g., mapping historic fires to nearest wx station)
- [ ] does front-end need styling to make it Gov of BC-compliant? (e.g., right now there's nothing on the page to indicate that it's a GovBC product)
- [ ] code cleanup - some dataframes/files are modified on the fly when they really should be cleaned up at source to match required format. This would improve performance
- [ ] have the option of implementing data caching to speed up performance

Some other steps that aren't necessarily MVP but have been requested:

- [ ] ability to compare between stations on one screen
- [ ] ability to download source data (in table) from app
- [ ] colour code dots on hourly fire index graphs to incidents where fires ignited
- [ ] ability to compare station_distance from historic fires across all years for a station - will help BCWS know where wx stations should be set up

The issue names no files, tests, or entry points. Begin by decomposing the checklist into separately scoped work for the front end, data-analysis scripts, source-data storage, testing, and performance, then identify the relevant project entry points. Done is not defined for the combined request; each resulting issue should specify its own acceptance criteria.

Written by the indexing model from the issue text.