quick update on test binaries

[Dirk Hohndel]

Hi Everyone

Looks like the 4.9.4 release didn't contain too many terrible bugs.
Or (more likely) no one is diving right now so no one is actually using any of this.
Case in point: number of active users (i.e., people who connected to the cloud 
backend in the last 30 days) is down more than 80% compared to January.

Anyway, one thing that became painfully obvious to me in the days working
towards the release (and then the complete failure to get release binaries) is 
that I shouldn't rely on GitHub to create the official binaries. I already had to
set up a web hook system to a VM running here at home that would build
working macOS binaries, so it wasn't all that hard to replicate the rest of the 
builds in my little Intel NUC based home data center :-)

As of today, there will no longer be CI releases on GitHub. I updated the scripts
(and the README) accordingly. Instead we are back to having binaries in
downloads/test - but now they are triggered by every push into master. And of 
course we also have binaries on OBS and Launchpad, all triggered by every push
through the same backend system that I built here.

If there's a specific binary that you need and that is missing, it's actually 
surprisingly easy to add additional builds / additional artifacts if those are 
useful to you. Just let me know.

For now this is what we have:

Subsurface-mobile-4.9.4.24-arm.apk
Subsurface-mobile-4.9.4.24-arm64.apk
subsurface-4.9.4-24-g744bad833a0f.exe
smtk2ssrf-4.9.4-24-g744bad833a0f.exe
Subsurface-4.9.4-24-g744bad833a0f-x86_64.AppImage
Subsurface-4.9.4-24-g744bad833a0f.dmg

32/64 bit Android packages
Subsurface and smtk2ssrf Windows installers
Linux AppImage
macOS DMG

Thanks

/D

PS: of course we are continuing to do test builds with GitHub Actions, so that
part of the CI setup stays unmodified. It's just the uploading of artifacts to 
GitHub releases that I turned off.