Release as github release with attestations and hashes

[baszalmstra]

Checklist

• I added a descriptive title
• I searched open requests and couldn't find a duplicate

What is the idea?

I would like to use the zig based launchers in rattler.

Ideally I would like to have the following in order of importance:

1. Support for x86, x64, and arm64.
2. Traceability
3. Signed binaries

This project already offers at least the first which is already better than the current status quo in rattler where we have none of these.

I would like to propose that we also build the (zig) launchers in this repository and publish them through github together with a sha256 hash. We can then use the built binaries in rattler, the hash should add at least some form of traceability.

We could also create SLSA attestations and publish those alongside the binaries.

Why is this needed?

We are currently using binaries of relatively unknown origin. There is no traceable information on how these binaries were built which poses a security risk.

What should happen?

No response

Additional Context

No response