Update CI tasks for newer Ubuntu versions and OS versions.

[teward]

Pre-submit checks

• [X] I checked for similar issues beforehand, but could not find any. I could not add my proposal to any existing issue.
• [X] I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise.

Feature description

Currenly all CI configurations here use Ubuntu Bionic 18.04. This EOL's next year (2023) unless you pay for an ESM subscription, which is not usable on Github.

To that end, I would like to see the CI tasks here updated to work with Ubuntu Focal which is the current LTS release of Ubuntu. I would also like to see other OS variants in the CI tests that won't hang up because of EOL releases or other problems (see the fact that for multiple pull requests, you have hung CI tasks everywhere)

Proposed solution

Update CI tasks and other tests to use supported OSes, and run test builds there. Consider external contribution for those if you need assistance (feel free to ask I'll happily make a PR that addresses changes needed in CI tasks).

Alternative solutions you considered

I've considered setting up automated CI tests on my own servers for CI (a-la Jenkins) to test build and test package the functionality on newer OSes, however that requires full manual intervention on my side, when this should be implemented in the local CI configurations for GitHub.

Additional context

No response

[TheAssassin]

This EOL's next year

And then, we'll move to the next LTS release.

The bionic-built packages are compatible to all newer releases of Ubuntu, as listed in the compatibility table. https://github.com/TheAssassin/AppImageLauncher#system-wide-installation

I would also like to see other OS variants in the CI tests

There are no tests, really. GitHub actions is used to provide packages mostly.

hang up because of EOL releases or other problems (see the fact that for multiple pull requests, you have hung CI tasks everywhere)

Like any free CI service, GitHub limits the concurrent executions quite a bit. The goal is to have less configurations, not more. The current builds are typically compatible to all newer releases of the corresponding distros.

see the fact that for multiple pull requests

These pull requests are out of date, and They'd have to update anyway, and that way would get an up to date CI configuration. This is not a valid argument IMO.

Some of these PRs have never seen a response again anyway.

---

Like when building AppImages, for works-everywhere packages, one has to build on old systems. The packages generated on Ubuntu 18.04 work on a variety of distributions. I personally use these packages on Ubuntu focal, Ubuntu 21.10 and openSUSE Leap on a couple of computers just fine. Therefore, moving to anything newer makes absolutely no sense until the current distribution is EOL.