revert crun workaround

[mxmxchere]

Same procedure as in gardenlinux/gardenlinux#2242

• gh-action: Removal of custom crun binary, Image
• gh-action: Removal of custom crun binary, Repo
• gh-action: Removal of custom crun binary, SysExts

---

• Starting with the GitHub image runner version 20240225.1.0 podman/crun stopped working correctly. Rough summary is that the used kernel and crun 0.17 did not play well together.
• @fwilhe introduced a workaround by using the binary release of crun 1.14.3
• The bug was fixed in ubuntu package 0.17+dfsg-1.1ubuntu0.1
• The workaround is most likely no longer needed. @fwilhe and I tested successfully with the current runner version (20240721.1.0, ubuntu-latest) and without the workaround
• I also checked that the current runner has crun 0.17+dfsg-1.1ubuntu0.1
• This PR reverts the workaround so that the crun version that comes with the runner image is used.

actions/runner-images#9425 (comment) (runner bugreport)
https://bugs.launchpad.net/cloud-images/+bug/2056442 (issue at ubuntu)
gardenlinux/gardenlinux@9f6f9c5 (workaround)
https://launchpad.net/ubuntu/+source/crun/0.17+dfsg-1.1ubuntu0.1 (fixed version)
https://github.com/fwilhe/jubilant-funicular/actions/runs/10197364403/job/28210045524 (@fwilhe 's run)
https://github.com/mxmxchere/gl-action/actions/runs/10196668968/job/28207883622 (my run)
https://github.com/mxmxchere/gl-action/actions/runs/10202473206/job/28226655108#step:2:15 (crun version output)

[fwilhe]

Thanks @mxmxchere. This repo is not maintained anymore and the failed builds don't relate to this PR. I'll archive the repo.