Modernize plugin tooling with uv, ruff, and mypy

[daviddavis]

The plugin template currently generates projects using black for code formatting and flake8 for linting. While these tools have served the ecosystem well, the Python tooling landscape has matured significantly, and several newer tools offer compelling advantages that plugin writers should be able to leverage.

I'd love to use some of the newer Python tooling we are using on other projects at our company like uv, ruff, and mypy. Maybe these tools could be offered on an opt-in basis where plugins could opt in to these tools? That way plugins could also choose to stay on black and flake8 if they don't want to use these newer tools.

[dralley]

This is already starting to happen FWIW, @gerrod3 transitioned the oci_env to UV last week, the CLI has been using UV (or was it Ruff?) for a while.

Anyway, I agree.

[mdellweg]

We are on it.
https://discourse.pulpproject.org/t/preview-toolchain-upgrade-black-flake8-ruff/2174

However in order to keep the ecosystem from fragmenting, I see a switch not an opt in...
We will do ruff first and then discuss whether to proceed with uv and maybe ty.

[daviddavis]

Cool, I tried switching our projects from mypy to ty but it seemed like ty lacked some features like mypy's strict mode. It's probably less of an issue for projects that don't currently use mypy though, and ty is incredibly fast compared to mypy.