add python 3.11 to ci

[wholmgren]

• 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.

[kandersolar]

@wholmgren bumping actions/setup-python from v1 to v4 made 3.11 available when I tried this a few days ago. After that, the blocker is that h5py hasn't yet released 3.11 wheels: h5py/h5py#2165

Also I think the new filename requirements-py-3.11.yml has an extra hyphen in py-3.11 that needs to be removed.

[wholmgren]

@kanderso-nrel thanks! should I close this in favor of a better developed branch of yours? feel free to push to this branch too.

[kandersolar]

Let's just keep this one

[kandersolar]

h5py 3.11 wheels are out! h5py/h5py#2146

[kandersolar]

LGTM! We should re-evaluate the commented-out packages in all the conda environment files at some point but doesn't have to be now.

[wholmgren]

@kanderso-nrel I cleaned up some CI specs. Worth another look. Then I think you can go ahead and merge.

[kandersolar]

We forgot to add 3.11 to the pytest-remote-data config, but otherwise LGTM. Thanks for the non-3.11 cleanup as well!