Update dependency numpy-stl to v3.2.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
numpy-stl	==3.1.2 -> ==3.2.0

---

Release Notes

WoLpH/numpy-stl (numpy-stl)

v3.2.0

Compare Source

Added numpy 2 support thanks in large part to JeffreyOI. With helps from @​tbaudier and @​JBil8

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: scripts/Plot/Pipfile.lock

Command failed: pipenv lock
Locking [packages] dependencies...
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Ignored the 
following yanked versions: 2.14.0
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Ignored the 
following versions that require a different python version: 3.2.0 
Requires-Python >3.9.0
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Could not 
find a version that satisfies the requirement numpy-stl==3.2.0 (from versions: 
1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.1.2, 1.2.0, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 
1.3.5, 1.3.6, 1.3.7, 1.3.8, 1.4.0, 1.4.1, 1.4.2, 1.5.0, 1.5.1, 1.5.2, 1.6.0, 
1.6.1, 1.6.2, 1.7.0, 1.7.1, 1.8.0, 1.9.0, 1.9.1, 2.0.0, 2.1.0, 2.2.0, 2.2.2, 
2.2.3, 2.3.0, 2.3.2, 2.4.1, 2.5.0, 2.6.0, 2.7.0, 2.8.0, 2.9.0, 2.10.0, 2.10.1, 
2.11.0, 2.11.1, 2.11.2, 2.11.3, 2.12.0, 2.13.0, 2.13.1, 2.14.1, 2.14.2, 2.15.0, 
2.15.1, 2.16.0, 2.16.1, 2.16.2, 2.16.3, 2.17.0, 2.17.1, 3.0.0, 3.0.1, 3.1.0, 
3.1.1, 3.1.2)
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2024.4.1/3.8.20/lib/python3.8/site-packages/pip
env/resolver.py", line 451, in main
[ResolutionFailure]:       _main(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2024.4.1/3.8.20/lib/python3.8/site-packages/pip
env/resolver.py", line 436, in _main
[ResolutionFailure]:       resolve_packages(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2024.4.1/3.8.20/lib/python3.8/site-packages/pip
env/resolver.py", line 400, in resolve_packages
[ResolutionFailure]:       results, resolver = resolve_deps(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2024.4.1/3.8.20/lib/python3.8/site-packages/pip
env/utils/resolver.py", line 967, in resolve_deps
[ResolutionFailure]:       results, hashes, internal_resolver = 
actually_resolve_deps(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2024.4.1/3.8.20/lib/python3.8/site-packages/pip
env/utils/resolver.py", line 735, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2024.4.1/3.8.20/lib/python3.8/site-packages/pip
env/utils/resolver.py", line 460, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=e)
Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: No matching distribution found for numpy-stl==3.2.0

Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: Failed to lock Pipfile.lock!