Linux: Do not package libmount &c

[mook-as]

In 1.17 release we had issues on Linux because we included too many shared libraries as part of the qemu dependencies (in the zip file / AppImage) and it no longer ran on Tumbleweed. We worked around it by manually deleting the file from the release zip file.

We should review the set of libraries we ship and improve the blacklist / change it to a whitelist / something.

For reference: https://github.com/rancher-sandbox/rancher-desktop-qemu/blob/f294295f2af10db6525322b8cb4a49ac80c3945c/appdir-qemu.sh#L51-L67

[mook-as]

We should also figure out what the criteria is for blacklisting libraries and document that.

[mook-as]

Tracked down the exclude list to have been derived from https://github.com/AppImageCommunity/pkg2appimage/blob/master/excludelist

Unfortunately, that now says to bundle GLib things. But digging further indicates that there's some argument on whether we should bundle that or not. It looks like bundling may break libsecret. But as we build on a newer system than some of the deploy targets (e.g. the Rocky users), we will need to ship it.

---

Trying to update the list to bundle the GLib files results in:

  libz.so.1
  libutil.so.1
  libm.so.6
  libgcc_s.so.1
  libpthread.so.0
  libc.so.6
  libresolv.so.2
  librt.so.1
  libuuid.so.1
  libdl.so.2

However, the AppImage doesn't work on Tumbleweed:

> ./rancher-desktop-9.main.1736453049.2503b4bd-Build2897.1.glibc2.34-x86_64.AppImage
rancher-desktop: symbol lookup error: /lib64/libgdk_pixbuf-2.0.so.0: undefined symbol: g_task_set_static_name

I think that means we need to do the reverse and bundle GLib (and see what issues we see).

I'm currently testing builds (from CI) against Rocky 9.5 + Tumbleweed, as being hopefully the two extremes.