Add binary releases via github actions

[jacksonrl]

Fixes https://issues.chromium.org/issues/409590665. See also https://issues.chromium.org/issues/409590665#comment6.

Here's an example of how the release would look: https://github.com/jacksonrl/dawn/releases/tag/v20251223.163459-jacksonrl.dawn.main The only difference is the name wouldn't have my name in it, which I think is autogenerated due to being a fork, and it would contain the macos/ios builds as well, which I disabled in my local version when testing due to low balance for macos runners (diff: jacksonrl/dawn@7d88c22...e53c2d0)

There are some ways we could improve the release outputs, but I wanted to make as minimal changes as possible to prevent any breakage as I cannot test all these platforms. Therefore this just uploads the output from the existing CI, which is mentioned in 409590665. These are nightly releases so nobody is expecting them to be stable, we can always improve this later

This also fixes the emdawnwebgpu release which was broken by 0979968 by removing wgpuTextureGetTextureBindingViewDimension from the emdawnwebgpu header. I'm not too familiar with the codebase so someone should please check that that is valid.

Motivation: Many people end up needing graphics at some point. Having prebuilt binaries allows people to choose WebGPU more readily, which strengthens the WebGPU ecosystem (eg. more libraries made with wglsl) and also allows people to potentially port their code to web at a later point.

cc @wcandillon

[github-actions]

👋 Thanks for your contribution! Your PR has been imported to Gerrit.
Please visit https://dawn-review.googlesource.com/c/dawn/+/282075 to see it and CC yourself on the change.
After iterating on feedback, please comment on the Gerrit review to notify reviewers.
All reviews are handled within Gerrit, any comments on the GitHub PR may be missed.
You can continue to upload commits to this PR, and they will be automatically imported
into Gerrit.

[jacksonrl]

@kainino0x (Responding to https://dawn-review.googlesource.com/c/dawn/+/282075/comment/df0a6726_a15314d5/)

Does this mean ci.yml will run twice on release commits, once when it is pushed and once when release.yml runs on schedule/dispatch? Or does it dedup with the existing run if there is one?

Yes, if I understood correctly, the release job will always run separately. I won't reuse the previous job on its own. However, the same effect can be achieved by implementing caching. We already have caching enabled for Linux but it doesn't appear to work, I think we need to use a different caching library that works and supports all platforms.

I wonder if instead of schedule we could do something like, pack everything into ci.yml, and when it runs on main, if there hasn't been a release in >24 hours, do a release?

Personally I think separating them is probably better, especially if we improve caching, but I haven't looked into this.

[github-actions]

🚀 PR was merged in e3231b9!

[kainino0x]

Oops just saw your comment here. Thank you for the suggestion, better caching sounds nice. I have filed https://crbug.com/473585665

BTW, let me know if you have any input on the proposed change in https://dawn-review.googlesource.com/c/dawn/+/283135!