add Python linting

[ThinkOpenly]

We should probably add some kind of Python linting (I'm a fan of Ruff) to CI/pre-commit to help with these kinds of things in the future.

Originally posted by @jordancarlin in #1231 (review)

[ThinkOpenly]

I tried ruff and pylint and results varied a bit. I intentionally added some things I knew pylint would catch.

$ ruff check tools/python
All checks passed!
$ $ pylint tools/python/*.py
************* Module udb
tools/python/udb.py:1:0: C0114: Missing module docstring (missing-module-docstring)
tools/python/udb.py:8:0: C0116: Missing function or method docstring (missing-function-docstring)
tools/python/udb.py:8:0: W0102: Dangerous default value [] as argument (dangerous-default-value)
[...]

What is actually checked is subjective, of course.

[jordancarlin]

Ruff is fairly configurable. Most of the rules from pylint can be enabled if desired, but Ruff also supports rules from most other popular linters and runs several orders of magnitude faster. See https://docs.astral.sh/ruff/rules/.

This is the list of rules I usually enable for Ruff:

[tool.ruff.lint]
select = [
  "F",    # various basic rules (pyflakes)
  "E",    # errors (pycodestyle)
  "W",    # warnings (pycodestyle)
  "I",    # Import related rules (isort)
  "UP",   # Upgraded version available in newer Python
  "B",    # bugbear rules
  "A",    # shadow builtins
  "EXE",  # Executable file shebangs
  "ANN",  # type annotation rules
  "RUF",  # Ruff specific rules
  "PTH",  # Pathlib usage
  "SIM",  # Simplifications
]

It might make sense to start with a fairly basic config, and then we can slowly enable more rules as we go so that we don't need to make significant changes to all of the Python code at once.