Option to allow a new release to be created if finalize does not find a matching commit

[klutchell]

An example I've seen many times in my personal repos:

1. PR opened by non-owner (user fork, dependabot, etc)
2. Deploy-to-balena action fails or is skipped as GH secrets are not available (API token, etc)
3. PR is merged anyway cause the code looks good
4. Finalize fails as no matching release exists

Why not add a new boolean flag to push a final release as a fallback for step 4 , or a more dynamic workflow param?

• workflow: draft - always push draft releases, and finalize on merge to master (current behaviour)
• workflow: auto - on merge/push to master check for existing release to finalize, otherwise push a new final release
• workflow: final - always push a new final release, from any branch

I know you have discussed workflows ad nauseam but I think this provides a really flexible alternative.