Fix numpy and altair version issues

[nfahlgren]

Describe your changes
There are some minor differences between numpy 1 and 2 keyword arguments. In #1687 we pinned to numpy >=2, but this prevents us from installing some things that still rely on numpy 1, and we don't need to be that restrictive if we modify the numpy function inputs to be more general, which is done in this PR. This PR also applies the altair v5 pin in the environment.yml file that was missed in #1845

Type of update
Is this a: Bug fix

For the reviewer
See this page for instructions on how to review the pull request.

• PR functionality reviewed in a Jupyter Notebook
• All tests pass
• Test coverage remains 100%
• Documentation tested
• New documentation pages added to plantcv/mkdocs.yml
• Changes to function input/output signatures added to updating.md
• Code reviewed
• PR approved

[deepsource-io]

Here's the code health analysis summary for commits 004a6a0..8dcd40f. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Test coverage	✅ Success		View Check ↗

Code Coverage Report

Metric	Aggregate	Python
Branch Coverage	100%	100%
Composite Coverage	100%	100%
Line Coverage	100%	100%
New Branch Coverage	100%	100%
New Composite Coverage	100%	100%
New Line Coverage	100%, ✅ Above Threshold	100%, ✅ Above Threshold

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[joshqsumner]

Works locally for me