Fix failing tests

[sam-watttime]

What

Fix failing tests

Why

To ensure that our tests pass so that we can run them every 30 minutes as a github action

How

Add pytz as a dependency annd replace hardcoded request start times

[sam-watttime]

Our tests were failing due to two issues:

1. our pandas dependency is open ended. Newer versions of pandas (3.0) no longer include pytz, which we rely on. This was added as a dependency.
2. We released new models for CAISO_NORTH, which is used as the test region. The new models do not have the same historical backfill (e.g. 2024 data). To fix this I changed hard coded dates in the tests to relative dates (e.g. one month ago). This may create more noise (e.g. due to intermittent data outages) if this becomes problematic in the future we could consider an alternative approach of using my-access to get the start data for the most recent model, and pull data bounded by that.

For now, this will fix failing tests and should be more robust to changes in the future.

[jcofield]

1. our pandas dependency is open ended. Newer versions of pandas (3.0) no longer include pytz, which we rely on. This was added as a dependency.

Note we are still allowing an unsupported python 3.8 so pytz could be necessary. I have added a task to upgrade this package to require python 3.10+ before we release it again.

[jcofield]

The nature of the tests here is to test dates which do not change, across 3 years of available data. It would change the nature of these tests to derivce dates at execution time. I suggest we keep the explicit use of a year (formely 2022, 2023, and 2024) and bump the hardcoded date years to valid years, i.e. 2025 and 2026. I have only attempted this for the sdk file but the tcy requires it a well.

[sam-watttime]

@jcofield tests are passing locally for me in my 3.11.15 venv. This matches the behavior of the github action which runs for each commit in this PR.

[sam-watttime]

After discussion, we went with a simpler solution of bumping years 2022, 2023 -> 2025 and 2024 -> 2026. All tests are passing now. This is in addition to adding the pytz dependency.

[nsteins]

LGTM. I think we should remove pytz from our code in the future, if we can, but that is a different PR