Add poa_ prefix to returned names when return_components=True in transposition functions

[kandersolar]

• Closes Add "poa_" prefix to return_components=True transposition model outputs #2529
• 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.

Note that pvfactors_timeseries (actually solarfactors under the hood) uses the old names, so the pvfactors tests are going to fail until solarfactors is updated and a new version released.

[ramaroesilva]

@kandersolar nice to see this moving! Will this be done also for isotropic, klucher, reindl, and king? I also noticed that the last two have "poa_" in the docstring but not on the actual variable within the code.

Also, I guess I should address #1553 (which is being handled here #2527) on top of this right? Once you comment on my first question (and it is addressed, if I'm right) I can later review this PR, so that its merging is sped up.

[kandersolar]

Will this be done also for isotropic, klucher, reindl, and king?

No, the idea here was to make only the breaking changes (changing returned dict key/dataframe column names), which only affect the functions that already have the return_components parameter. To be clear, these two sets of changes are related, but can be done independently in parallel:

1. The breaking change of renaming the component column names for haydavies, perez, and perez_driesse (this PR)
2. The enhancement of adding return_components to the other functions (starting with Adapts irradiance.isotropic to return_components framework. #2527)

Better to keep them separate because smaller, focused PRs are easier to review, and because it means we can be sure to get the breaking changes into the next release (a .0 release) even if the enhancements aren't ready in time.

I also noticed that the last two have "poa_" in the docstring but not on the actual variable within the code.

The names of actual variables in the code are not user-facing, so strictly speaking it doesn't matter if they match the docstring (or anything else). If we want to change them to have poa_ for code clarity then that's fine, but that's orthogonal to achieving #1553.

Also, I guess I should address #1553 (which is being handled here #2527) on top of this right? Once you comment on my first question (and it is addressed, if I'm right) I can later review this PR, so that its merging is sped up.

Hopefully the above addresses this :) These two changes can be worked on independently. I do think this PR achieves the intended scope and is ready for review though.

[cwhanse]

I thought the discussion in #2529 indicated that this change would happen in v0.14, since its breaking?

[kandersolar]

The imminent release, which was once called v0.13.2, will be v0.14.0 instead. The whatsnew will be renamed in the release PR, and I need to clean up the milestones too.

[kandersolar]

CI is green after I retriggered everything following making a new solarfactors release (v1.6.1) with compatibility for this change.