`pyproject.toml` `required-version` or minor version support

Hey guys,

A common way I've seen `uv` used in larger projects is to set the following section to protect against unforseen changes in minor version bumps of the tool

`pyproject.toml`
```
...
[tool.uv]
required-version = "~=0.12.0"
...
```

This prevents devs from requiring the perfect `uv` version installed, but also protects the project from odd CI / dev env inconsistencies since plugins like `setup-uv` in GitHub Actions will read and install the `required-version` auto-magically.

Can we get either:

1. An automagical version resolution from the `pyproject.toml` (path-configurable with repo-root default), and/or
2. Minor version tags in this repo which are kept up to date with the latest matching patch tags (ie. `rev: 0.12` -> `rev 0.12.11` as of time of posting)?

The former seems to be the "unified" way - the latter is a relaxed option.

Start with the proposed [tool.uv] required-version setting in pyproject.toml and review how setup-uv currently discovers it in GitHub Actions. Compare automatic version resolution with maintaining minor-version tags, then define which behavior and update rules would count as complete.

Written by the indexing model from the issue text.