chore: migrate dependency management to uv

[rpocase]

PR Checklist

To ease the process of reviewing your PR, do make sure to complete the following checklist before submitting a pull
request.

• I have added unit tests to cover the new behavior under ``tests/unit_tests/```
• I have run tox -e format locally to automatically format my code before submitting
• I have run tox locally ensuring that it passes before submitting
• [-] (if applicable) I have added a reference to issues that this PR relates to in the PR message (Refs GH-1234, Fixes GH-1234)
• My commits are atomic and follow the convetional commit message format (https://www.conventionalcommits.org/en/v1.0.0/)

Otherwise, please leave the PR as a draft to indicate that it is still a work in progress.

Description

this change migrates dependencies to be properly managed by uv instead of specified in requirements files,
upgrades mypy, and fixes newly found type hinting issues. this is in preparation for upgrading
openstack-sdk as netiface is orphaned and should be migrated to netiface2

Additional Context and Relevant Issues

this was triggered in part because running mypy was failing because of a missing typed-ast package.
at the same time, i've upgraded mypy and resolved all new type hinting issues.

Test Steps

N/A? i think integration tests should be run, but i don't have a proper setup to facilitate this

[Copilot]

Pull request overview

Migrates the project from legacy requirements/setup.cfg packaging to a pyproject.toml-driven build (Hatchling) and dependency management aligned with uv, while updating type hints/signatures to satisfy a newer mypy.

Changes:

• Replaced setup.py/setup.cfg + requirements*.txt with PEP 621 metadata and extras in pyproject.toml (Hatchling backend).
• Updated tox, Read the Docs config, and a CI workflow step to install dependencies via extras/uv instead of requirements files.
• Adjusted several cloud/instance method signatures to accept **kwargs and tightened example type annotations for mypy.

Reviewed changes

Copilot reviewed 18 out of 19 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
tox.ini	Switches tox deps to install via project extras rather than requirements files; updates lint/typecheck targets.
test-requirements.txt	Removes legacy test requirements list (moved into pyproject.toml extras).
setup.py	Removes legacy setuptools entry point.
setup.cfg	Removes legacy package metadata and dependency declarations.
requirements.txt	Removes legacy “-e .” requirements indirection.
pyproject.toml	Adds PEP 621 project metadata, dependencies, optional extras, and tool configs; switches build backend to Hatchling.
pycloudlib/openstack/instance.py	Updates method signature to accept **kwargs for interface compatibility.
pycloudlib/oci/cloud.py	Adds **kwargs to selected APIs for signature compatibility.
pycloudlib/lxd/instance.py	Adds **kwargs to lifecycle methods; threads get_pty through _run_command.
pycloudlib/lxd/cloud.py	Adds **kwargs to snapshot signature for interface compatibility.
pycloudlib/gce/instance.py	Adds **kwargs to wait_for_delete signature for interface compatibility.
pycloudlib/ec2/cloud.py	Adds **kwargs to snapshot signature for interface compatibility.
examples/oracle/oracle-cluster-demo.py	Uses Optional[str] for nullable parameters to satisfy mypy.
examples/ibm_classic.py	Uses Optional[str] for nullable parameters to satisfy mypy.
docs/requirements.txt	Removes legacy docs requirements list (moved into pyproject.toml extras).
ci-requirements.txt	Removes legacy CI requirements list.
.readthedocs.yaml	Switches RTD install method to uv and uses the docs extra.
.github/workflows/version_check.yaml	Installs uv and uses it to install packaging for version checking.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[rpocase]

@blackboxsw if you have a moment

[holmanb]

Why uv rather than pip?

[rpocase]

Why uv rather than pip?

1. i misread the repo and thought it was using uv to manage installation but wasn't using pyproject.toml for dependency management
2. more modern tooling that is become increasingly pervasive
3. we should look at integrating AGENTS.md and providing a sandboxing environment. i would go with workshops. the only supported path forward to easily bootstrap is with the uv plugin. it would have to be a lot more customized if we stuck with pip