feat: add action to upload pre-compiled artifacts

[lima-limon-inc]

Describe your changes

Closes 0xMiden/midenup#179

With this PR, after a release is made, pre-compiled artifacts are automatically added to the corresponding Github release page. This is used on midenup in order to speed installs up.

Attribution note: This added step was taken from the compiler's CI and adapted for the miden-vm.

Follows up on 0xMiden/miden-client#1936

[bitwalker]

There are actually two artifacts that we want to produce from this workflow, as part of publishing a release:

1. The miden-vm executable, which this PR does currently
2. The core.masp package file, produced by the build script of the miden-core-lib crate. We may need a dedicated Makefile task for this though, since there isn't an easy way to locate the build script output directory without capturing the verbose output of cargo build in JSON form. We could either modify the build script to output the .masp to both OUT_DIR and CARGO_TARGET_DIR/core.masp (so that we have a predictable location to obtain it from), or write a cargo script that links against miden-core-lib and writes the embedded package bytes to disk somewhere. Either way, we'll need that artifact as well.