FIX: update pre-commit image to current ubuntu latest

[ZLLentz]

The ubuntu-20.04 image runs python 3.8 which is too old for some of the twincat pre-commit builds.

Rather than keep using the old image, I opted to update to the 22.04 image that is currently tagged as "ubuntu-latest".
I could have also chosen 24.04 but since it wasn't tagged as latest I decided to only go up to 22.04.

List of builds:
https://github.com/actions/runner-images/tree/main

I then tried to run pre-commit on CI on a repo that was previously failing.
Failing build: https://github.com/pcdshub/lcls-twincat-math/actions/runs/11582459856/job/32245532359
My passing build: https://github.com/ZLLentz/lcls-twincat-math/actions/runs/11710367753/job/32616497674

I did not try this again on the python repos but I expect this to be transparent.
I am not currently interested in updating all the builds because that has some (low) risk of creating havoc and I'm not ready for that today.

Ref https://jira.slac.stanford.edu/browse/ECS-6684

[tangkong]

This LGTM, though I'm a bit confused how we only ran into this now, after being off 3.8 for years and the offending check being around for 5ish months. I guess we don't run that much twincat CI?

[tangkong]

Once this is merged I can re-run a python pre-commit test to check. (I conveniently left an atef PR open)

[ZLLentz]

This happened now because Roald added new checks in pcdshub/pre-commit-hooks#29 and we didn't take advantage of them until Nick tried them out in pcdshub/lcls-twincat-math#1.

So, this is currently the only repo of ours using this check, hence only learning about it now.

Any other consumers using this check would have had no issues if they were already using ubuntu-latest.

[tangkong]

Ah of course, the pre-commit runs using the repo's config. makes total sense