Update pre-commit config

[jank324]

Description

Update alle versions in .pre-commit-config.yaml.

Motivation and Context

Closes #147.

• [x] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation (update in the documentation)

Checklist

• [x] I have updated the changelog accordingly (required).
• [ ] My change requires a change to the documentation.
• [ ] I have updated the tests accordingly (required for a bug fix or a new feature).
• [ ] I have updated the documentation accordingly.
• [x] I have reformatted the code and checked that formatting passes (required).
• [x] I have have fixed all issues found by flake8 (required).
• [x] I have ensured that all pytest tests pass (required).
• [ ] I have run pytest on a machine with a CUDA GPU and made sure all tests pass (required).
• [x] I have checked that the documentation builds (required).

Note: We are using a maximum length of 88 characters per line

[jank324]

So @cr-xu, I'm not sure if this is a satisfactory solution. Basically, the versions of rev are not allowed to be dynamic. For now, I've updated them. We would have to keep updating them whenever a version mismatch leads to a mismatch between the pre-commit hook and the respective GitHub Action. This would be a little work ... but the mismatch would inherently alert us when it needs doing.

[cr-xu]

okay it makes sense. I think breaking changes in these linting tools happen only more or less on a yearly basis so it wouldn't be so annoying.