Finalize 0.10.4

[kandersolar]

• Closes v0.10.4 release planning #1992
• 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.

Leaving as draft while reviewing the various CI jobs

[kandersolar]

Inspecting the test output, I see a few warnings like this:

  /Users/runner/work/pvlib-python/pvlib-python/pvlib/inverter.py:535: FutureWarning: ChainedAssignmentError: behaviour will change in pandas 3.0!
  You are setting values through chained assignment. Currently this works in certain cases, but when using Copy-on-Write (which will become the default behaviour in pandas 3.0) this will never work to update the original DataFrame or Series, because the intermediate object on which we are setting values will behave as a copy.
  A typical example is when you are setting values in a column of a DataFrame, like:
  
  df["col"][row_indexer] = value
  
  Use `df.loc[row_indexer, "col"] = values` instead, to perform the assignment in a single step and ensure this keeps updating the original `df`.
  
  See the caveats in the documentation: https://pandas.pydata.org/pandas-docs/stable/user_guide/indexing.html#returning-a-view-versus-a-copy
  
    coeffs['a'][d] = a

and many warnings like this:

  /Users/runner/work/pvlib-python/pvlib-python/pvlib/tests/test_temperature.py:257: FutureWarning: 'H' is deprecated and will be removed in a future version, please use 'h' instead.

The former is coming from inverter.py, so inside pvlib itself. I'm not immediately seeing a hard release date for pandas 3.0, but it might be as early as April 1 (https://github.com/pandas-dev/pandas/milestone/102), so before our next release. I will submit a PR to fix those in this release.

The latter is from the tests, so lesser priority to fix, but easy enough so might as well.

[AdamRJensen]

Remember to add docs/sphinx/source/whatsnew/v0.10.5.rst

[kandersolar]

I'll proceed with making the release. Many thanks as always to all contributors!