Unpin the max matplotlib version, which upgrades numpy

[opotowsky]

What is the change?

TL;DR: fixed some numpy and python deprecation issues, and deleted the max matplotlib pin for py311 and up.

Unpinning the max matplotlib pin in ARMI opened some floodgates for other upgrades, specifically numpy. I ended up with one test failing in test_historyTracker.py because some zeroes were being saved as np.int64 in the database and that was getting processed into strings when using getHistory. So that's where those forced int() pieces came from. The rest is self explanatory numpy deprecation warnings.

Why is the change being made?

matplotlib v3.8 being the max version doesn't always work with higher python versions. The pip resolution in github actions is not behaving the same elsewhere. So let's just fix root cause of the max pin instead.

---

Checklist

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

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

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

[john-science]

Okay, I see broken tests. But I like the IDEA of the PR, and am happy to support it in whatever way you need.

[opotowsky]

Okay, I see broken tests. But I like the IDEA of the PR, and am happy to support it in whatever way you need.

Yep I'm just playing around trying to find a set of deps that works with the unpinned matplotlib for higher python versions.

Right now py39 and py310 are failing, as expected. I have to find the place in the code responsible for returning the np.int64 dudes and force an int, otherwise we are close!

[opotowsky]

@john-science This is ready now! let me know if it's important enough for the release notes. I guessed "no" but I'm willing to be wrong.

[john-science]

Great! Thanks so much!