chore: prevent gh release edit from automatically setting release as latest
`gh release edit` behavior marks the release as latest even with
`gh release edit --latest=false --draft=false`
Doing this via `gh api` results in the desired behavior. The release
will be marked as latest by the post-announce custom job if necessary.