Update project configuration for UV integration and Python version

[zoola969]

No description provided.

[Copilot]

Pull Request Overview

This PR migrates the project from using pip/hatch to UV for dependency management and build tooling. The changes standardize on UV as the primary package manager while maintaining compatibility with the existing Python project structure.

Key changes:

• Replaces pip-based dependency management with UV's dependency groups
• Updates build system to use UV with dynamic versioning
• Migrates CI/CD workflows to use UV commands instead of pip/hatch

Reviewed Changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
pyproject.toml	Converts optional dependencies to UV dependency groups and configures UV dynamic versioning
.python-version	Adds Python version specification for UV
.github/workflows/tests.yml	Updates test workflow to use UV for dependency installation and command execution
.github/workflows/publish.yml	Simplifies publish workflow to use UV build instead of hatch
.github/dependabot.yml	Changes package ecosystem from pip to uv for automated dependency updates

Comments suppressed due to low confidence (3)

pyproject.toml:7

• Black version 25.1 does not exist. The latest stable version of Black is in the 24.x series. Consider using "black~=24.10" or a similar existing version.

    "black~=25.1",

pyproject.toml:15

• MyPy version 1.17 does not exist. The latest stable version of MyPy is in the 1.11.x series. Consider using "mypy~=1.11" or verify the correct version.

    "mypy~=1.17",

.github/workflows/tests.yml:17

• Python 3.14 has not been released yet. The latest stable Python version is 3.13. Consider removing "3.14" from the test matrix or use "3.14-dev" if you specifically want to test against development versions.

        python-version: ["3.9", "3.10", "3.11", "3.12", "3.13", "3.14"]