feat: allow release based on git hash

[aeneasr]

Related Issue or Design Document

Checklist

• I have read the contributing guidelines
  and signed the CLA.
• I have referenced an issue containing the design document if my change
  introduces a new feature.
• I have read the security policy.
• I confirm that this pull request does not address a security
  vulnerability. If this pull request addresses a security vulnerability, I
  confirm that I got approval (please contact
  security@ory.sh) from the maintainers to push
  the changes.
• I have added tests that prove my fix is effective or that my feature
  works.
• I have added the necessary documentation within the code base (if
  appropriate).

Further comments

[kevgo]

Can you document what this feature is intended for, when this should be used and when not? Could there be two releases with the same release number but different hashes, like v0.1.0-pre.0 75484 and v0.1.0-pre.0 7838? Why not make the latter one v0.1.0-pre.1?

[aeneasr]

We don't always want to release HEAD of master but instead a git tag form e.g. a few days ago. That's what this feature is for!