Add options for token override, draft releases and supplying release tag

[manue1]

As part of the release of an upcoming CLI extension in which the built binary gets uploaded to a secondary repository instead of the one in which the code resides the following options were added:

• allow creating a draft release
• allow supplying a github_token input parameter in order to allow using a token other than github.token
• allow supplying a pre-created release tag

[andyfeller]

@manue1: Thank you for the contribution!

Would like to delve into a couple aspects of these changes a little more deeply. I appreciate however you can help me understand the improvement these bring 🙇

[andyfeller]

@manue1 : Could you elaborate on this approach versus deriving the tag from the reference? Is there an example you can share that showcases a concrete example and how others might benefit from this change?

[manue1]

We have a use case for an upcoming CLI extension where the code resides in one repo and has the built binaries published to another separate repo. (see workflow)

Our current plan is to trigger the release manually by dispatching the workflow since it would follow the GHES release window. Instead of creating a release tag in the source repo we'd therefore solely create the tag in the destination repo and GITHUB_REF would therefore not be set when the workflow is run.

I'm also unsure if this is a use case that many others will benefit from. 🤔

[andyfeller]

@manue1 : thank you for your patience!

@samcoe : did you have any final call outs?

[samcoe]

LGTM! Thanks for making the requested changes.