Use dev dependency versions in pre-commit, uncap most dev dependencies, improved min dependency versions

[bmos]

What is this change?

• Update development dependencies to latest versions using >= syntax without upper version limits (except where appropriate to avoid saddling developers with updating format/syntax (ruff) of code they don't touch)
• Refactor pre-commit config to use the same versions defined in pyproject.toml (no more risk of them getting out of date!)
• Update library dependencies to match the lowest versions that were actually usable
• Fix pytest cache key not including pyproject hash
• Remove ruff, bandit, and sphinx-lint exceptions from dependabot
• Remove unused "vendor" exceptions from tooling
• Update dependabot config to only propose updates for python development dependencies, docker images, and github actions -- actual program dependencies will remain unchanged as we want to support a wide range of versions

Considerations for discussion

• pre-commit config will now only work if the dev dependencies are installed
• are there other dev dependencies we want to have maximum version limits on to ensure reproducibility?
• all PRs that modify pyproject.toml will have the dependencies label applied, is this desirable?

How to test the changes (if needed)

• see pre-commit ci workflow log

Breaking Changes

Breaking changes are changes to our public API which may require existing users to change their code. If there are no breaking changes, any existing parsons user should not need to do anything after updating their parsons version.

Does this PR introduce breaking changes?

• label: Breaking change — This PR introduces one or more breaking changes.
• label: Non-breaking change — This PR does not introduce one or more breaking changes.

Details (if needed)

• (List out any changes to the API that may cause breaks for developer implementation.)

[github-actions]

Coverage report

This PR does not seem to contain any modification to coverable code.