Update test_meteonorm expected values for new year

[kandersolar]

• [ ] Closes #xxxx
• I am familiar with the contributing guidelines
• Tests added
• [ ] Updates entries in docs/sphinx/source/reference for API changes.
• [ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
• [ ] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
• Pull request is nearly complete and ready for detailed review.
• Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

Latest remote-data tests are failing with (See https://github.com/pvlib/pvlib-python/actions/runs/21646769714/job/62400674396):

FAILED tests/iotools/test_meteonorm.py::test_get_meteonorm_training
requests.exceptions.HTTPError: Meteonorm API returned an error:
invalid time range: make sure 'start' and 'end' are in the range 2024-01-01T00:00:00Z ... 2026-01-27T20:37:28Z`

Meteonorm docs say that "Available time period: the current year excluding the last 7 days, plus the latest two full calendar years."

This PR updates the requested dates and associated expected values to follow this requirement.

[kandersolar]

I won't bother anyone for a review for such a trivial fix. Merging...