Make sure uv.lock in breeze corresponds to pyproject.toml #43684
Description
When you manually modify breeze's pyproject.toml, the uv.lock might not correspond to the changes you've just added. Breeze manages installation automatically when you run it, so when you use uv tool it should use the .lock, so whenever we modify pyproject.toml we should also make sure uv sync is run to reflect that.
This can be done with a pre-commit. The uv sync should only modify lock if pyproject.toml changed (unles --frozen option is used for uv sync - so we should be able to safely run uv lock in pre-commit for breeze, just to make sure no changes in pyproject.toml should be reflected in the lock file.