Dependabot tries to bump min version to latest release

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Package ecosystem

pip

### Package manager version

_No response_

### Language version

_No response_

### Manifest location and content before the Dependabot update

_No response_

### dependabot.yml content
```
version: 2
updates:
- package-ecosystem: "pip"
# This workflow should use the python version specified in
# .python-version file.
directory: "/" # Location of package manifests
schedule:
interval: "daily"
labels: ["dependencies", "skip_changelog", "run_benchmarks"]
groups:
# group similar dependencies together into fewer PRs
docs:
patterns:
- "sphinx"
linting:
patterns:
- "flake8"
- "black"
- "pre-commit"
testing:
patterns:
- "pytest"
- "qic"
- "qsc"
- "shapely"
minor_packages:
patterns:
- "colorama"
- "nvgpu"
- "psutil"
- "pylatexenc"
- "termcolor"
jax:
patterns:
- "jax"
- "diffrax"
- "interpax"
- "interpax_fft"
- "orthax"
- "quadax"
- "jax-finufft"
- package-ecosystem: "github-actions"
directory: "/"
schedule:
# Check for updates to GitHub Actions every week
interval: "weekly"
```
### Updated dependency

_No response_

### What you expected to see, versus what you actually saw

Recently, dependabot started to create PRs to bump the minimum version specified in my requirements file. This is very annoying because I still want to support those versions. For example PR, see https://github.com/PlasmaControl/DESC/pull/2179, https://github.com/PlasmaControl/DESC/pull/2178, https://github.com/PlasmaControl/DESC/pull/2176/changes, https://github.com/PlasmaControl/DESC/pull/2161/changes.

Updates to the max version were working properly until recently.

### Native package manager behavior

_No response_

### Images of the diff or a link to the PR, issue, or logs

For example PR, see https://github.com/PlasmaControl/DESC/pull/2179, https://github.com/PlasmaControl/DESC/pull/2178, https://github.com/PlasmaControl/DESC/pull/2176/changes, https://github.com/PlasmaControl/DESC/pull/2161/changes.

### Smallest manifest that reproduces the issue

_No response_

Start with the dependabot.yml shown in the report and inspect the linked DESC pull request diffs alongside the project's requirements file. Trace how the pip ecosystem interprets minimum and maximum version constraints, then look for existing tests covering grouped dependency updates. Done means reproducing the unwanted minimum-version bump and preventing it while preserving the expected maximum-version behavior.

Written by the indexing model from the issue text.