Does not start on Ubuntu 24.04+ due to Electron issue with sandboxing

[Hellgartner]

Describe the bug
OpossumUI AppImage does not start on Ubuntu 24.04+

To Reproduce
Steps to reproduce the behavior:

1. Open any machine (or VM) running Ubuntu 24.04
2. Download the most recent release (the AppImage version)
3. Try to open the AppImage via double clicking
4. Confirm sandbox access
5. AppImage does not open
6. Opening the AppImage via command line yields

hellgartner@dominikus-metavm:~/programs/opossumUI$ ./OpossumUI-for-linux.AppImage 
[5523:0108/081918.385987:FATAL:setuid_sandbox_host.cc(163)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_Opossu8S9j6E/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)

Expected behavior
App image does open

Screenshots

Desktop (please complete the following information):

• OS:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.1 LTS
Release:        24.04
Codename:       noble

The test system is a KUbuntu system but given the links in the additional context as well as the failures for the e2e tests observed in #2704 this should be observable for all Ubuntu 24.04+ systems.

Additional context

• Opening the AppImage works if you deactivate the sandbox:

  ./OpossumUI-for-linux_test.AppImage --no-sandbox

• This is an issue with Electron AppImages conflicting with the new Ubuntu sandboxing of AppImage. Corresponding issue from Electron
  [Bug]: All versions of Electron (chromium upstream bug) fail to open on Ubuntu 24.04+ due to kernel.apparmor_restrict_unprivileged_userns=1 by default electron/electron#41066
• Electron-builder managed to solve this for installation via .deb but this remains unresolved for AppImages as the path to an AppImage is not defined, see Add apparmor profile electron-userland/electron-builder#8635 (comment)

[Hellgartner]

Ideas/Thoughts

• Waiting for Electron is possibly difficult as this is already open since 01/2024 --> no quick fix expected
• Alternative solution:
  • Switch to another deployment variant for linux
  • electron-builder supports e.g. snap
  • This would mean
    • Change the configuration
    • Adapt e2e test instructions and pipelines

[Hellgartner]

When fixed, please also make sure to remove the exception for renovate bot
#2708