Chore/fix ci

[ClemensElflein]

No description provided.

[ClemensElflein]

Requesting review from @docgalaxyblock and @Apehaenger because you both worked on the CI issue. @docgalaxyblock says its a good idea to keep the builder on -latest, but the clang-format failed due to version mismatch, this seems to fix it.

(Also specifying is a good idea, because on Discord we had some confusion about formatting rules with differing clang-format versions)

[Apehaenger]

I would also prefer to go with -latest instead of getting antique by time.
In fact I also tried to examine how, but all I found, sound wired (like set to python@3 instead of python@3.x.x), so I ugly switched to ubuntu-22.04 because it was obvious that the new -latest (24.x) was the reason for the failing CI.

Specifying the clang-format version is also preferable, even though I couldn't identify what really happen in the discussed issue at Discord. But similar already happen before #141 (comment)

I'm unsure about if you didn't already tested switching the auth username to github.actor during last try, but I even don't know how to test without merging 😇

[docgalaxyblock]

OK give it a short check and my commits are already included in #152 where the github.actor did not worked and I therefore force-pushed the commit out again.

I would remove all commits except 28e4b38 and then add my discovered fixes for the 24.04/latest based runner.

Edit: like here

[ClemensElflein]

force pushed your linked commits to this pr

[docgalaxyblock]

Looks good, the Workflow also succeeded.