Adding some version limits to our Dependencies

[john-science]

What is the change?

I did some dependency testing in ARMI.

I ran all our CI (linting, tests, and docs) on Windows and Linux, in Python 3.7 - 3.11, and tested what versions of our dependencies we really need.

Results:

• I set some lower bounds on versions of all our dependencies that ARMI can fully support.
• I found 3 ARMI dependencies that ARMI had that it didn't use:
  • configparser
  • pillow
  • xlrd

Why is the change being made?

This is just clean up, but as clean up work goes it's important. The changes I made to our pyproject.toml file don't actually change ARMI. They just make the truth about ARMI more visible.

---

Checklist

• [X] This PR has only one purpose or idea.
• [X] Tests have been added/updated to verify any new/changed code.

• [X] The code style follows good practices.
• [X] The commit message(s) follow good practices.

• [X] The release notes have been updated if necessary.
• [X] The documentation is still up-to-date in the doc folder.
• [X] The dependencies are still up-to-date in pyproject.toml.