new rule - detect uv dev dependencies being used in production code

in my project, i was importing from dev dependencies in intended to be used by users of my module:

```py
# public_module.py
from foo import bar
```
```py
# pyproject.toml
[tool.poetry.group.dev.dependencies]
foo = "^1.0.0"
```

because of this, all my tests were passing because the dependency existed, but the moment a user tried to use it, it crashed because the module was not installed.

it would be nice if ruff had a rule to detect this like [this eslint plugin does](https://github.com/import-js/eslint-plugin-import/blob/v2.27.5/docs/rules/no-extraneous-dependencies.md)

Reproduce the example using public_module.py and pyproject.toml, then check how Ruff’s current import rules handle it. Done means Ruff reports production imports whose packages are declared only under [tool.poetry.group.dev.dependencies], without flagging valid imports.

Written by the indexing model from the issue text.