Consider modernizing build system to use hatch or uv

[tleonhardt]

There are several more advanced build system tools which are worth exploring. The current default recommendation from python seems to be hatch. It has impressive features including declaring build/test configurations and managing venv environments. @anselor tried hatch on a couple small projects and found it to be much faster than using nox to set up venvs. The problem is it currently doesn't support a monorepo project with multiple modules or plugin modules. There is a development ticket (pypa/hatch#233) that documents it and it is under active development now. Once that is complete we should be able to migrate to hatch with minimal fuss.

A newer alternative that is taking the Python world by storm is uv which is an extremely fast Python package and project manager, written in Rust. uv is a single tool to replace pip, pip-tools, pipx, poetry, pyenv, virtualenv, pipenv and more. I've used this at work to replace pip in some builds and it has typically sped things up by a factor of 2x.

[tleonhardt]

#1367 added support for uv venvs.
#1368 fixed a few bugs with that above

uv virtual envs are now working great for cmd2 development on both the master and 3.0.0 branches.

[tleonhardt]

TODO:

• Replace use of nox in GitHub Action pytest runs with uv
• Remove use of nox in tasks.py
• Remove dependency on nox
• Replace use of twine in tasks.py with uv publish
• Remove dependency on twine

[tleonhardt]

#1370 Replaces the use of nox in GithHub Action pytest runs with uv, removes nox from tasks.py and removes the dependency on nox