Deprecate and disable data_version parameter in get_meteonorm_tmy

[AdamRJensen]

• I am familiar with the contributing guidelines
• I attest that all AI-generated material has been vetted for accuracy and is in compliance with the pvlib license
• Tests added
• 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.

The remote data tests are currently failing due to the get_meteonorm_tmy function no longer supporting the data_version parameter.

[AdamRJensen]

The change is documented in the meteonorm changelog: https://docs.meteonorm.com/overview/changelog-api#2025-12-05

[kandersolar]

We can deprecate this with a message "this parameter no longer has any effect (see XX meteonorm URL) and will be removed soon", right? Can we do that instead of jumping straight to removal?

[AdamRJensen]

We can deprecate this with a message "this parameter no longer has any effect (see XX meteonorm URL) and will be removed soon", right? Can we do that instead of jumping straight to removal?

The issue is that the API requests are currently failing when the parameter is included.

[kandersolar]

Right. Can't we keep it as a parameter to the pvlib function (to avoid a breaking change), and just stop including it in the API request?

[kandersolar]

Here are the changes I'm suggesting. Ideally there would also be a test to verify the deprecation warning.

[echedey-ls]

LGTM, minor whatsnew nitpick down below. I'll add this change to #2396.

[kandersolar]

Test failure unrelated