CI: pre-commit autoupdate to fix CI
new click release broke previous version of `black`, see https://github.com/psf/black/issues/2964
I assume will will get the same error on 1.4.x? > I assume will will get the same error on 1.4.x?

hmm, merged #46550 a couple of hours ago after the problem was noticed on main. pre-commit was green on 1.4.x. more investigation required. I think it's just that on the 1.4.x branch the run used the old cached dependencies:
```
Cache Size: ~63 MB (65887285 B)
```
which would've had the previous `click` version

Don't know how long the cache lasts, but I think this should probably be backported > OK to merge once Code Checks / pre-commit is green 

merging then Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
git checkout 1.4.x
git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
git cherry-pick -x -m1 8f442441e02f7239fd7d34c2e177a39125062e05
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
git commit -am 'Backport PR #46558: CI: pre-commit autoupdate to fix CI'
```

4. Push to a named branch:

```
git push YOURFORK 1.4.x:auto-backport-of-pr-46558-on-1.4.x
```

5. Create a PR against branch 1.4.x, I would have named this PR:

> "Backport PR #46558 on branch 1.4.x (CI: pre-commit autoupdate to fix CI)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                 @meeseeksdev backport 1.4.x Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
git checkout 1.4.x
git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
git cherry-pick -x -m1 8f442441e02f7239fd7d34c2e177a39125062e05
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
git commit -am 'Backport PR #46558: CI: pre-commit autoupdate to fix CI'
```

4. Push to a named branch:

```
git push YOURFORK 1.4.x:auto-backport-of-pr-46558-on-1.4.x
```

5. Create a PR against branch 1.4.x, I would have named this PR:

> "Backport PR #46558 on branch 1.4.x (CI: pre-commit autoupdate to fix CI)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                