Improve profile parsing for simulations #55
Description
It may be worth improving the way skypro handles load profiles.
Profiles are currently represneted as historical datasets - this is handy because it's easy to bring 'actuals' over and use them in Skypro simulations.
At the moment we are searching based on an exact time match, i.e. if we are simulating 2025-04-10T12:30:00 then the profile is searched for a value at that exact time, if that exact time is not found then *2024*-04-10T12:30:00 is looked for, then 2023 etc, until a match is made.
This approach gets us 80% of the way there, but it isn't perfect:
- Clock changes happen on different dates each year, so searching by UTC time, and just updating the year, isn’t quite right
- Searching by local time may be better
- Do we want an awareness of weekends/weekdays - these aren't on the same dates every year. Load profiles can vary significantly between weekends and weekdays.
- Leap years are issues: Feb 29th gets zero profiles
- It might be simpler to assume that the 29th Feb never exists