[Pacific Power] Look into fixing missing data uploads

Related parent issue

(dated February 5)

Although this is dated February 5, the latest shown data is from February 3, when it should show up to February 4. Issue also seemed inconsistent between meters, and time of day (this particular meter showed data up to February 4 later in the day on February 5)

The "monthly_top_text" variable in the current scraper code returns output like Period2024-02-04Average Temperature42.0Usage(kwh)2388.30Est. Rounded Amount$253
- Increasing the value at the end of the original selector (e.g. changing the selector value to end with tr:nth-child(2) instead of tr:nth-child(1) results in an output of one day previous, e.g. Period2024-02-03Average Temperature43.5Usage(kwh)2625.21Est. Rounded Amount$266 (February 3 vs 4)
- We can read the date from pacificpower site directly as seen above, and validate this against the expected date value

First: check pacificpower site directly via manual testing, see if there are any buttons or menus to reliably refresh frontend state (pacificpower site is bulit on angular)
second: PacificPower shows date for each data row (date as actually shown on their site), so use that date instead. Run validation as shown below
third: See if we can implement checking on energy dashboard backend / database
- approach 1 (kind of like multiple SQL queries on backend, put stress on backend / database): Send POST request of last 5 days or so of data to energy dashboard backend. Have energy dashboard backend perform SELECT queries on data and upload any non redundant data
- approach 2 (put stress on webscraper side, await more GET request): Add a new download route to pacificpower data to find most recent data point for a pacificpower meter (maybe without requiring start and end dates like current meter download route). Then, make GET request to energy dashboard backend from webscraper for each meter, check for which data is missing and needs to be uploaded, before sending any POST
- A new GET (download) route will be required, because the current /data?id=... route only considers data linked to the meters table, and not all Pacific Power Data will be linked to meters table (new meters or redundant meters etc)