Revert numpy2 testing commit so we can release

[stscirij]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.41%. Comparing base (8eb63d1) to head (85bfef1).
Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #240      +/-   ##
==========================================
- Coverage   87.64%   87.41%   -0.23%     
==========================================
  Files          17       17              
  Lines        1392     1367      -25     
==========================================
- Hits         1220     1195      -25     
  Misses        172      172              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[zacharyburnett]

just FYI, this will work for the next few weeks, but when Numpy 2 is released on the 19th, any users who try to run calcos with numpy>=2.0.0 installed will get a runtime error that looks like this:

A module that was compiled using NumPy 1.x cannot be run in
NumPy 2.1.0.dev0 as it may crash. To support both 1.x and 2.x
versions of NumPy, modules must be compiled with NumPy 2.0.
Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.

If you are a user of the module, the easiest solution will be to
downgrade to 'numpy<2' or try to upgrade the affected module.
We expect that some modules will need time to support NumPy 2.

https://github.com/spacetelescope/calcos/actions/runs/9417921200/job/25944177737?pr=240#step:10:205

Since all the tests appear to run fine when the calcos wheel is built with Numpy 2 (see the most recent CI run on master), from what I can see there is no harm in keeping this set to numpy>=2.0.0rc2 until the release, after which we can update it to numpy>=2.0.0 if necessary.