Provide better flexibility around GitHub releases

If we're confident enough to publish a binary to a catalog environment (whichever it is), the corresponding GitHub release should exist too. This would:
- Provide transparency about what's deployed where
- Let users/testers download the artifact directly
- Align the GitHub releases with catalog state
The releases could be marked as pre-releases for non-prod environments, or drafts that get promoted to "latest" on prod. This would let us consolidate back to the shared workflows while keeping the early-release workflow we need.

Proposed solution:
- Dev, Ops and Canary CD Actions all build a draft release if it doesn't yet exist
- Prod CD action builds a published release if it doesn't exist, or publishes it if it does

- [ ] Figure out how to handle tags
- [x] Input to handle draft
- [ ] Input to handle pre-release
- [ ] Consider adding an input for the release body/changelog