Update numpy requirement from <2.1.0,>=1.16.6 to >=1.16.6,<2.3.0 in /…

…tests (#28402)

Updates the requirements on [numpy](https://github.com/numpy/numpy) to
permit the latest version.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/numpy/numpy/releases">numpy's
releases</a>.</em></p>
<blockquote>
<h2>2.2.1 (DEC 21, 2024)</h2>
<h1>NumPy 2.2.1 Release Notes</h1>
<p>NumPy 2.2.1 is a patch release following 2.2.0. It fixes bugs found
after the 2.2.0 release and has several maintenance pins to work around
upstream changes.</p>
<p>There was some breakage in downstream projects following the 2.2.0
release due to updates to NumPy typing. Because of problems due to MyPy
defects, we recommend using basedpyright for type checking, it can be
installed from PyPI. The Pylance extension for Visual Studio Code is
also based on Pyright. Problems that persist when using basedpyright
should be reported as issues on the NumPy github site.</p>
<p>This release supports Python 3.10-3.13.</p>
<h2>Contributors</h2>
<p>A total of 9 people contributed to this release. People with a
&quot;+&quot; by
their names contributed a patch for the first time.</p>
<ul>
<li>Charles Harris</li>
<li>Joren Hammudoglu</li>
<li>Matti Picus</li>
<li>Nathan Goldbaum</li>
<li>Peter Hawkins</li>
<li>Simon Altrogge</li>
<li>Thomas A Caswell</li>
<li>Warren Weckesser</li>
<li>Yang Wang +</li>
</ul>
<h2>Pull requests merged</h2>
<p>A total of 12 pull requests were merged for this release.</p>
<ul>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/27935">#27935</a>:
MAINT: Prepare 2.2.x for further development</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/27950">#27950</a>:
TEST: cleanups</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/27958">#27958</a>:
BUG: fix use-after-free error in npy_hashtable.cpp (<a
href="https://redirect.github.com/numpy/numpy/issues/27955">#27955</a>)</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/27959">#27959</a>:
BLD: add missing include</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/27982">#27982</a>:
BUG:fix compile error libatomic link test to meson.build</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/27990">#27990</a>:
TYP: Fix falsely rejected value types in
<code>ndarray.__setitem__</code></li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/27991">#27991</a>:
MAINT: Don't wrap <code>#include &lt;Python.h&gt;</code> with
<code>extern &quot;C&quot;</code></li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/27993">#27993</a>:
BUG: Fix segfault in stringdtype lexsort</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/28006">#28006</a>:
MAINT: random: Tweak module code in mtrand.pyx to fix a Cython...</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/28007">#28007</a>:
BUG: Cython API was missing NPY_UINTP.</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/28021">#28021</a>:
CI: pin scipy-doctest to 1.5.1</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/28044">#28044</a>:
TYP: allow <code>None</code> in operand sequence of nditer</li>
</ul>
<h2>Checksums</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/numpy/numpy/blob/main/doc/RELEASE_WALKTHROUGH.rst">numpy's
changelog</a>.</em></p>
<blockquote>
<p>This is a walkthrough of the NumPy 2.1.0 release on Linux, modified
for
building with GitHub Actions and cibuildwheels and uploading to the
<code>anaconda.org staging repository for NumPy
&lt;https://anaconda.org/multibuild-wheels-staging/numpy&gt;</code>_.
The commands can be copied into the command line, but be sure to replace
2.1.0
by the correct version. This should be read together with the
:ref:<code>general release guide &lt;prepare_release&gt;</code>.</p>
<h1>Facility preparation</h1>
<p>Before beginning to make a release, use the
<code>requirements/*_requirements.txt</code> files to
ensure that you have the needed software. Most software can be installed
with
pip, but some will require apt-get, dnf, or whatever your system uses
for
software. You will also need a GitHub personal access token (PAT) to
push the
documentation. There are a few ways to streamline things:</p>
<ul>
<li>Git can be set up to use a keyring to store your GitHub personal
access token.
Search online for the details.</li>
<li>You can use the <code>keyring</code> app to store the PyPI password
for twine. See the
online twine documentation for details.</li>
</ul>
<h1>Prior to release</h1>
<h2>Add/drop Python versions</h2>
<p>When adding or dropping Python versions, three files need to be
edited:</p>
<ul>
<li>.github/workflows/wheels.yml  # for github cibuildwheel</li>
<li>tools/ci/cirrus_wheels.yml # for cibuildwheel aarch64/arm64
builds</li>
<li>pyproject.toml  # for classifier and minimum version check.</li>
</ul>
<p>Make these changes in an ordinary PR against main and backport if
necessary.
Add <code>[wheel build]</code> at the end of the title line of the
commit summary so
that wheel builds will be run to test the changes. We currently release
wheels
for new Python versions after the first Python rc once manylinux and
cibuildwheel support it. For Python 3.11 we were able to release within
a week
of the rc1 announcement.</p>
<h2>Backport pull requests</h2>
<p>Changes that have been marked for this release must be backported to
the
maintenance/2.1.x branch.</p>
<h2>Update 2.1.0 milestones</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/numpy/numpy/commit/7469245786b57405b7ae264b386400061b3b25d3"><code>7469245</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/28047">#28047</a>
from charris/prepare-2.2.1</li>
<li><a
href="https://github.com/numpy/numpy/commit/acb051e2a3fc90c687079dbe8a8b56c2af507eb3"><code>acb051e</code></a>
REL: Prepare for the NumPy 2.2.1 release [wheel build]</li>
<li><a
href="https://github.com/numpy/numpy/commit/28a091a4efde3488b20355d6b6ad7100d2c64076"><code>28a091a</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/28044">#28044</a>
from charris/backport-28039</li>
<li><a
href="https://github.com/numpy/numpy/commit/723605bcaf472514fbb34947e5b61daa135c0769"><code>723605b</code></a>
TST: Add test for allowing <code>None</code> in operand sequence passed
to <code>nditer</code></li>
<li><a
href="https://github.com/numpy/numpy/commit/554739ee490013cf2757c1ef1420d120d607836b"><code>554739e</code></a>
TYP: allow <code>None</code> in operand sequence of nditer</li>
<li><a
href="https://github.com/numpy/numpy/commit/31bc4c8b8ec732582e2a0513afd105b594d15d95"><code>31bc4c8</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/28021">#28021</a>
from charris/backport-28020</li>
<li><a
href="https://github.com/numpy/numpy/commit/32f52a37bc0f7ba3ab0321e57ba8719c15848772"><code>32f52a3</code></a>
CI: pin scipy-doctest to 1.5.1 (<a
href="https://redirect.github.com/numpy/numpy/issues/28020">#28020</a>)</li>
<li><a
href="https://github.com/numpy/numpy/commit/6219aeb6f6d1d8be54339401c3634b9d7a6c063e"><code>6219aeb</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/28007">#28007</a>
from charris/backport-28005</li>
<li><a
href="https://github.com/numpy/numpy/commit/eb7071ca103cf8cfbd5a61ce2ef2bb21fb9638a0"><code>eb7071c</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/28006">#28006</a>
from charris/backport-28003</li>
<li><a
href="https://github.com/numpy/numpy/commit/4f82c3262f8a0a0229d0483b53e47694118b32a5"><code>4f82c32</code></a>
BUG: Cython API was missing NPY_UINTP.</li>
<li>Additional commits viewable in <a
href="https://github.com/numpy/numpy/compare/v1.16.6...v2.2.1">compare
view</a></li>
</ul>
</details>
<br />


Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

tests/constraints.txt

@@ -1,4 +1,4 @@
-numpy>=1.16.6,<2.1.0
+numpy>=1.16.6,<2.3.0
 attrs==24.2.0
 distro==1.9.0
 h5py>=3.1.0,<3.12.0