Dependabot suggests version bump that conflicts with version spec in pyproject.toml

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Package ecosystem

pip (Poetry)

### Package manager version

_No response_

### Language version

Python 3.13

### Manifest location and content before the Dependabot update

[/pyproject.toml](https://github.com/DonDebonair/slack-machine/blob/main/pyproject.toml)

[/poetry.lock](https://github.com/DonDebonair/slack-machine/blob/main/poetry.lock)

### dependabot.yml content

https://github.com/DonDebonair/slack-machine/blob/main/.github/dependabot.yml

### Updated dependency

- Dependency: `aiohttp`
- From: 3.10.11
- To: 3.11.2

Happens in [this PR](https://github.com/DonDebonair/slack-machine/pull/1205)

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

I expect Dependabot _not_ to suggest an update to `aiohttp` because of the following line in `pyproject.toml`:

```toml
aiohttp = ">=3.8.5,<3.11.0"
```

The version currently specified in `poetry.lock`:

```toml
[[package]]
name = "aiohttp"
version = "3.10.11"
```

This is the last version available before 3.11.0

What I actually saw: Dependabot opening [this PR](Happens in [this PR](https://github.com/DonDebonair/slack-machine/pull/1205)

### Native package manager behavior

Shell output of Poetry:

```
$ poetry show aiohttp
name : aiohttp
version : 3.10.11
description : Async http client/server framework (asyncio)

dependencies
- aiohappyeyeballs >=2.3.0
- aiosignal >=1.1.2
- async-timeout >=4.0,<6.0
- attrs >=17.3.0
- frozenlist >=1.1.1
- multidict >=4.5,<7.0
- yarl >=1.12.0,<2.0

required by
- aiobotocore >=3.9.2,<4.0.0

$ poetry update aiohttp
Updating dependencies
Resolving dependencies... (12.5s)

No dependencies to install or update
```

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

_No response_

### Smallest manifest that reproduces the issue

_No response_

Start by tracing Dependabot's pip (Poetry) update handling for the constraints in pyproject.toml and the resolved version in poetry.lock. Reproduce the aiohttp update from 3.10.11 to 3.11.2 and verify that the version specifier <3.11.0 prevents an update PR from being opened.

Written by the indexing model from the issue text.