Release workflow post-merge fixes

[hrls]

• make release only from tag from tags release-v* and devnet pushes
• always latest
• shorten commit SHA in release name
• fix macOS flow
• bundle both Linux and macOS releases into single release archive

Release is always triggered from a manual tag.

Using this release action is a bit confusing when we try to release from branch. A tag is required anyway. And pushing new commits to a branch updates the binary in an existing release, but not the source code.

[hrls]

Can we keep releases on devnet triggered by pushes?

Done