pre-commit autoupdate

[cclauss]

What do these changes do?

Perhaps land #749 first.

$ pre-commit autoupdate

Updating https://github.com/pre-commit/pre-commit-hooks ... updating v4.0.1 -> v4.3.0.
Updating https://github.com/asottile/yesqa ... already up to date.
Updating https://github.com/PyCQA/isort ... updating 5.10.0 -> 5.10.1.
Updating https://github.com/psf/black ... updating 22.3.0 -> 22.6.0.
Updating https://github.com/pre-commit/pre-commit-hooks ... updating v4.0.1 -> v4.3.0.
Updating https://github.com/asottile/pyupgrade ... updating v2.29.0 -> v2.37.1.
Updating https://github.com/PyCQA/flake8 ... already up to date.
Updating https://github.com/Lucas-C/pre-commit-hooks-markup ... already up to date.

Are there changes in behavior for the user?

Related issue number

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• Add a new news fragment into the CHANGES folder
  • name it <issue_id>.<type> (e.g. 588.bugfix)
  • if you don't have an issue_id change it to the pr id after creating the PR
  • ensure type is one of the following:
    • .feature: Signifying a new feature.
    • .bugfix: Signifying a bug fix.
    • .doc: Signifying a documentation improvement.
    • .removal: Signifying a deprecation or removal of public API.
    • .misc: A ticket has been closed, but it is not of interest to users.
  • Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.