Upload to GitHub Releases when artifacts become available

[Nifury]

Update the CI pipeline so that:

1. It first creates a release draft.
2. Artifacts are uploaded to the draft as soon as they are generated.
3. Mark the release as ready once all artifacts have been created.

It should work based on my mock test: https://github.com/Nifury/test-artifact/actions/runs/19835202594

Fixes #517 (comment).

P.S.
I just realized the simplest fix might be to increase the retention period instead...

[teeminus]

What's the most robust way to fix our issue? This PR or increasing the retention period?

[Nifury]

I'm leaning slightly towards this PR.
Besides, I don't have access to change the retention period setting.

[teeminus]

Do we have to manually clean up pre-releases when a pipeline fails?

[PF4Public]

Besides, I don't have access to change the retention period setting.

Is it a repo setting?

[Nifury]

Do we have to manually clean up pre-releases when a pipeline fails?

I pushed a commit to fix this.

Is it a repo setting?

Nope, it is set in the code..(by me...)

ungoogled-chromium-windows/.github/actions/stage/index.js

Line 58 in e1e3f95

'C:\\ungoogled-chromium-windows\\build', {retentionDays: 1, compressionLevel: 0});

How about I close this PR and just adjust the retention period instead? That seems simpler, and the original logic is already well-tested.

[teeminus]

I think this PR is more elegant as it publishes the files once they are available. However, if adjusting the retention period fixes the problem as well I am fine with that as well.

If adjusting the retention period does not fix the issue we can still use this PR.

[teeminus]

I increased the retention time for the next release: #520

If that does not fix the pipeline I tend to merge this.