chore: add ruff to QA checks

[maxrake]

ruff is the hot new linter for Python. It is written in Rust and is extremely fast. It also has tremendous support and constant updates. It replaces some of the existing (pyupgrade) and planned (e.g., bandit, flake8, isort, and pylint) QA tools that are outlined in #14. More new rules are added all the time. The initial configuration enables ALL rules by default and then selectively ignores specific rules based on conflicts, preference, and existing issues in the backlog.

Using ALL has the risk that new rules may be enabled when ruff is updated but updates are automated, with a PR that includes enforced QA checks, to weekly dependency and pre-commit hook bumps. Therefore, the real risk is that a developer on this project may have a local version of ruff installed that is newer than the one used for the pre-commit hook. That should limit the exposure to no more than a week of "early" rules and may still result in improved code quality.

The list of actions taken in this PR include:

• Add a custom ruff configuration in pyproject.toml
  • All rules are enabled by default
  • Specific rules and rule sets are disabled
• Remove the pyupgrade pre-commit hook
  • Those checks are covered by ruff
• Add the ruff pre-commit hook
  • This will enforce the rules in the QA check
• Enable GitHub PR annotations for any findings
• Add noqa comments, with reasons, where appropriate
• Sort imports based on the isort configuration
• Adhere to PEP-257 docstrings everywhere
• Update the CONTRIBUTING guide to discuss QA expectations
• Make updates to resolve all outstanding findings
• Add a black badge to the README to show the formatting style used

Related to #14

[andreaphylum]

Looks good to me. All the lint-related changes are simple enough and don't change the semantics.