Better Snapshot Dependency Handling

The plugin has a simple snapshot dependency resolution mechanism.
When a snapshot dependency is found, it allows for setting it to release... but it does not allows to choice the release version to use:

<code>
Resolve Project Dependency Snapshots.: 'com.sinapsi.libs:sinapsi-commons' set to release? (yes/no) yes: : yes
What is the next development version? (2.1.3-SNAPSHOT) 2.1.3-SNAPSHOT: :
</code>

in this case the versions are:
current: 2.1.2-SNAPSHOT
release: 2.1.2
next: 2.1.3-SNAPSHOT

The problem is that the only allowed development version is 2.1.3-SNAPSHOT (the value between the parentheses), hence the only allowed release version is 2.1.2.
Notably, you cannot specify an OLDER relase (such as 2.1.1): this means you are forced to release the dependency (you cannot use an already released version).

It would be better to ask for the release version to use, and then set the snapshot as the release following the release version specified by the user:

<code>
Resolve Project Dependency Snapshots.: 'com.sinapsi.libs:sinapsi-commons' set to release? (yes/no) yes: : yes
What is the release version? 2.1.2: : 2.3.0
</code>

in this case the versions are:
current: 2.1.2-SNAPSHOT
release: 2.3.0
next: 2.3.1-SNAPSHOT

The plugin suggests to set the release version to 2.1.2, but the user can choice another version, eventually an already released version.