build(deps): update scipy requirement from <1.15.0,>1.0.0 to >1.0.0,<…

…1.16.0 in /requirements (#2898)

build(deps): update scipy requirement in /requirements

Updates the requirements on [scipy](https://github.com/scipy/scipy) to permit the latest version.
- [Release notes](https://github.com/scipy/scipy/releases)
- [Commits](scipy/scipy@v1.0.1...v1.15.0)

---
updated-dependencies:
- dependency-name: scipy
  dependency-type: direct:production
...

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

requirements/image.txt

@@ -1,6 +1,6 @@
 # NOTE: the upper bound for the package version is only set for CI stability, and it is dropped while installing this package
 #  in case you want to preserve/enforce restrictions on the latest compatible version, add "strict" as an in-line comment
 
-scipy >1.0.0, <1.15.0
+scipy >1.0.0, <1.16.0
 torchvision >=0.15.1, <0.22.0
 torch-fidelity <=0.4.0  # bumping to allow install version from master, now used in testing

requirements/nominal_test.txt

@@ -4,5 +4,5 @@
 pandas >1.4.0, <=2.2.3 # cannot pin version due to numpy version incompatibility
 dython ==0.7.6 ; python_version <"3.9"
 dython ~=0.7.8 ; python_version > "3.8"  # we do not use `> =`
-scipy >1.0.0, <1.15.0 # cannot pin version due to some version conflicts with `oldest` CI configuration
+scipy >1.0.0, <1.16.0 # cannot pin version due to some version conflicts with `oldest` CI configuration
 statsmodels >0.13.5, <0.15.0

requirements/segmentation_test.txt

@@ -1,6 +1,6 @@
 # NOTE: the upper bound for the package version is only set for CI stability, and it is dropped while installing this package
 #  in case you want to preserve/enforce restrictions on the latest compatible version, add "strict" as an in-line comment
 
-scipy >1.0.0, <1.15.0
+scipy >1.0.0, <1.16.0
 monai ==1.3.2 ; python_version < "3.9"
 monai ==1.4.0 ; python_version > "3.8"