Remove g_poa_effective renamed kwarg warning in pvsystem.pvwatts_dc()

[RDaxini]

• Closes Remove g_poa_effective renamed kwarg warning in pvsystem.pvwatts_dc() #2703
• 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
• 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.

Also removes variable from the nomenclature page

[RDaxini]

Tagged as 0.15.1 but the wrapper did allow users to use the old arg name, as well as emit a warning, so do we class it as a breaking change for 0.16.0...?

[AdamRJensen]

Tagged as 0.15.1 but the wrapper did allow users to use the old arg name, as well as emit a warning, so do we class it as a breaking change for 0.16.0...?

I would say yes, this should go in 0.16.

[AdamRJensen]

@RDaxini Could you also remove the term from the nomenclature? It's a bit of a scope creep, but I think it fits nicely here 😄

[kandersolar]

The next release is 0.16.0, so let's merge this. @RDaxini can you update from main and resolve the conflict?

[RDaxini]

conflicts didn't show on git desktop so 82d5270 messed up the whatsnew. 22d00dc should fix that now

[RDaxini]

Thanks for helping to fix the whatsnew @kandersolar; I confess I only had a quick look at that one as I was working on a few things at the same time.
Feel free to ping me / request review on any priority PRs that require additional support to move them forward specifically for 0.16.0, which I imagine we are planning to release very soon.

[kandersolar]

for 0.16.0, which I imagine we are planning to release very soon

Not really. We can do it any time, but the current plan is mid-September :) My recent flurry of activity is just catching up after being away for a while.