Publish short-lived nightly builds for changes worth to test

[eirnym]

it's an extension for #227 to publish (maybe) short lived pre-releases to test specific feature. This would help alpha- and beta-testers to test specific feature without installation of the whole setup. Results can also be used to test on variety of systems for some user experience features and find edge cases.

[boozook]

Not sure why that needed in current state.
Most of tools here uses SDK and/or Rust/LLVM toolchain, so you're need "full setup" almost anyway.

I've created #227 just to speed up integration test on CI and probably for those rare users who wants precompiled binary rather than build the optimal binary for their system.

Also, there's couple open questions:

• What criteria to stale build or pre-release? How long it should be existing?
• What exactly should be built and so way released? What branches, binaries?

Anyway I would appreciate it if you create PR with it.

[eirnym]

This project has regular releases (defined by releases page), so I see #227 to build a package with pre-build binary packages for these releases.

In some cases it's required to create a pre-release to test a small feature and test if feature/build is working in a field (for manual testing opposing to the CI) or not.

These pre-releases may live before feature is stabilised and removed after the nearest release.

[eirnym]

I imagine the process as follows:

• developer creates an unstable feature
• maintainer create a pre-release and asks to test it
• tester returns and tells if feature is working properly
• if feature isn't working, process repeats and feature is marked as "more stable"

[boozook]

Okay, I've made it in the #262 and previously #231.

No prereleases, just artefacts attached to workflow-run, there for example.

All artefacts built with debug info and stored for 3 days.