Workflow correction for wayland AppImage generation

[saswatdash65]

I am adding a fix for the Wayland issue in the AppImage creation.

As we can just install the Qt5 libraries from official packages, I removed jurplel/install-qt-action@v3 and unified the Install Qt step for both x86_64 and aarch64. Added qtwayland5 to be installed for Wayland build.

I removed https://github.com/probonopd/linuxdeployqt from CI, as it breaks the Wayland builds and also adds base system libraries in the package (which the AppImage recommends excluding from packaging). Instead I used https://github.com/linuxdeploy/linuxdeploy and the qt plugin https://github.com/linuxdeploy/linuxdeploy-plugin-qt. It already excludes most base system libraries and I excluded some more base system libraries which it doesn't exclude.

The build will likely work on most systems.

[SaschaWillems]

The build will likely work on most systems.

The issue with that: The caps viewer is also part of the LunarG SDK. So changes like these must be checked on all target platforms beforehand.

Can you guarantee that Linux builds will still work with this PR for the way how they're packaged with the LunarG SDK?

[saswatdash65]

I only modified the build of AppImages of Wayland and X11 uploaded on the website. So this only affects the AppImage creation.
VulkanCapsViewer included in Vulkan SDK usually doesn't find any surfaces which means they don't define DEFINES+=X11 or DEFINES+=WAYLAND in their build system. Lunarg might have their own build system.

[saswatdash65]

I have updated the build system for both Wayland and X11 builds. Some Linux core system libraries needed to be excluded from the build. Now it compiles and will work on all Linux distros that support the libraries of the GitLab CI build system (Ubuntu 22.04).