[SCSB-155] build with Numpy 2.0 release candidate

[zacharyburnett]

resolves SCSB-155

Numpy 2.0 is scheduled for release on June 19th. Due to the C ABI updates, Python projects that build C extensions are required to build against Numpy 2.0 in order to use Numpy 2.0 in runtime.
This is backwards-compatible with Numpy versions in runtime as far back as 1.26

this PR pins numpy>=2.0.0rc2 in build-system.requires

Note

this PR was generated automatically by batchpr 🤖

Checklist

• added entry in CHANGES.rst (either in Bug Fixes or Changes to API)
• updated relevant tests
• updated relevant documentation
• updated relevant milestone(s)
• added relevant label(s)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.73%. Comparing base (af5aefb) to head (b16a9e7).
Report is 9 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #260      +/-   ##
==========================================
- Coverage   85.18%   83.73%   -1.46%     
==========================================
  Files          35       35              
  Lines        6797     6990     +193     
==========================================
+ Hits         5790     5853      +63     
- Misses       1007     1137     +130     

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

[braingram]

Thanks for opening this PR! @zacharyburnett I pushed a change to this PR renaming the now missing NPY_NTYPES to NPY_NTYPES_LEGACY in a debugging function. I believe this is the only change required to build with numpy 2.0 (the CI now passes, checking locally it works). Would you add a changelog to this PR and queue up regression tests (I think just making sure it works with runtime numpy <2.0 makes sense as other dependencies will need to be updated for runtime numpy >=2.0)?

[zacharyburnett]

JWST regtest running against this branch at https://github.com/spacetelescope/RegressionTests/actions/runs/9350842575/job/25735604033

[braingram]

I started roman regtests here: https://plwishmaster.stsci.edu:8081/job/RT/job/Roman-Developers-Pull-Requests/803/
All ran without errors with this PR and numpy 1.26.4

[zacharyburnett]

the GHA JWST test had some errors, but I'm not sure if those are due to unresolved issues in the GHA or this PR, so I ran on Jenkins here: https://plwishmaster.stsci.edu:8081/blue/organizations/jenkins/RT%2FJWST/detail/JWST/2913/pipeline

[zacharyburnett]

are these failures relevant? https://plwishmaster.stsci.edu:8081/blue/organizations/jenkins/RT%2FJWST/detail/JWST/2913/tests

[braingram]

I don't think so. They match the ones from the previous run (which used stcal main):
https://plwishmaster.stsci.edu:8081/blue/organizations/jenkins/RT%2FJWST/detail/JWST/2912/tests

[braingram]

Thanks!