Pin numpy versions <2.0

[kkappler]

Description

"numpy>=1.24,<2"
in setup.py.

1.24 is the highest version that is compatible with python 3.8

Motivation and Context

When installing from git clone and then pip, which looks at setup.py, the lack of a pinned version was allowing numpy>2. This is still a problem with simpeg, so to work around it we pin numpy <2.

How Has This Been Tested?

Run the tests in mtpy-v2
Run the tests in aurora (which pip install mtpy-v2 from github)

Screenshots (if appropriate):

Types of changes

• [X ] Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the code style of this project.
• I have added tests to cover my changes.
• All new and existing tests passed.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 33.66%. Comparing base (797a922) to head (7c1a29a).
Report is 3 commits behind head on updates.

Additional details and impacted files

@@           Coverage Diff            @@
##           updates      #62   +/-   ##
========================================
  Coverage    33.66%   33.66%           
========================================
  Files          146      146           
  Lines        24144    24144           
========================================
  Hits          8129     8129           
  Misses       16015    16015           

Flag	Coverage Δ
tests	33.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[Patrick-Cole]

Is there any plan to relax this requirement? My numpy is greater than 2 and I would like to use mtpy-v2