Resolve an Issue to an Unreleased Version

### Problem Statement

I want to be able to resolve issues to an unreleased application version.

### Solution Brainstorm

Couple things for context first:
- My team at the moment is using a rule to specify “Fix version” on Jira tickets, which would be `2.4.0`, `2.4.100`, `2.5.0`, etc. We do that whenever Jira ticket is created from within Sentry as well.
- The development builds are marked with `SNAPSHOT`, i.e. `2.4.0-SNAPSHOT`

The ideal workflow:
1. A Jira ticket is created or linked with a Sentry issue
2. Jira ticket is assigned “Fix version” value of `2.4.0`
3. Whenever Jira ticket is complete/closed it triggers “resolve” in Sentry (it already does)
4. Sentry resolves an issue for any `2.4.0` release. Keep in mind `2.4.0-SNAPSHOT` is a different version name so it does not apply. Also note it applies on any build number as long as Jira ticket specifies version name only.
5. Sentry looks for regressions against `2.4.0`, of which there are none until the version is actually available.

The ideal workflow described above we would use with each issue/crash resolution as it would essentially be fully automated.

┆Issue is synchronized with this [Jira Improvement](https://getsentry.atlassian.net/browse/FEEDBACK-1697) by [Unito](https://www.unito.io)