Allow NumPy v2.0+

[michaelcdevin]

Description

With autograd being updated to work with NumPy v2.0 as of autograd v1.7.0 (yay!), we can now remove the version limitation for NumPy. This required updating a few references to variable aliases that NumPy v2 removes, but should still be compatible with earlier NumPy versions.

Type of PR

• Bug fix
• New feature
• Documentation
• Other: (specify)

Checklist for PR

• Authors read the contribution guidelines
• The pull request is from an issue branch (not main) on your fork, to the dev branch in WecOptTool.
• The authors have given the admins edit access
• All changes adhere to the style guide including PEP8, Docstrings, and Type Hints.
• Modified the documentation if applicable
• Modified or added a new test
• All tests pass
• Reference or close any relevant issues

[michaelcdevin]

I'm keeping this as a draft for now due to some issues with wavespectra cooperating with newer versions of NumPy on Conda, see wavespectra/wavespectra#145. Because wavespectra doesn't have an explicit NumPy <2.0 designation (even though it is still downgrading for some reason), it doesn't downgrade other WecOptTool dependencies, which breaks the CI. So hold off on merging this until the upstream issue with wavespectra is resolved.

[michaelcdevin]

Error I'm seeing while running tests/test_integration.py if you're curious:

Windows fatal exception: code 0xWindows fatal exception: code 0xc06d007f

Thread 0x00000b90 (most recent call first):
  File "C:\Users\mcdevin\AppData\Local\miniforge3\envs\wot_py312_conda\Lib\site-packages\numpy\core\numeric.py

I believe numeric.py was one of the "problem modules" that caused autograd to break with NumPy v2.0 originally, so I think the NumPy downgrade due to wavespectra (without it downgrading other packages) is the culprit here.