Use vpk package with old AppImage runtime

[smoogipoo]

Closes ppy/osu#30187

It turns out that the new AppImage runtime does not play nice with an external tool called AppImageLauncher, which simply doesn't seem to support the type-2 runtime: AppImage/type2-runtime#12

Resulting in many projects experiencing the same/similar issues:

• Latest .deb no longer works with Ubuntu 24.04.1 TheAssassin/AppImageLauncher#657
• Some AppImage app not being executed TheAssassin/AppImageLauncher#656
• Flameshot AppImage doesn't start, squashfs image uses (null) compression TheAssassin/AppImageLauncher#602
• AppImageLauncher breaks starting AppImages because mounting fails TheAssassin/AppImageLauncher#599
• Not running AppImages TheAssassin/AppImageLauncher#593
• Installing AppImageLauncher breaks Endless-Sky 0.10.2 AppImage TheAssassin/AppImageLauncher#586
• error: [appimagelauncher-binfmt-bypass/interpreter] ERROR: execv(�e, ...) failed TheAssassin/AppImageLauncher#564

And now, osu!.

Velopack switched to type-2 upon request, because we wanted to use zstd compression. This was my mistake, because we were actually using zlib (which is mapped to by gzip). The PRs involved were:

• Use zstd compression for appimage (#221) velopack/velopack#237
• Make appimage compression algorithm configurable velopack/velopack#238
• Include new type2 appimage runtime and set default compression to zstd velopack/velopack#243

I will be PRing the revert to Velopack upstream, but in the meantime I've built a custom package from https://github.com/smoogipoo/velopack/tree/revert-type2-runtime + https://github.com/smoogipoo/velopack/actions/runs/11274894456

@peppy I intend to rebuild the existing release on Linux ASAP to prevent more issues like ppy/osu#30187

I have tested that it runs, but I don't have AppImageLauncher installed so have not reproed the original issue.

[smoogipoo]

Velopack PR: velopack/velopack#257

[peppy]

Linux and iOS are trying hard to top each other for your valuable dev time 🙈