[MRELEASE-897] support multiple release versions

**[Romain Manni-Bucau](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rmannibucau)** opened **[MRELEASE-897](https://issues.apache.org/jira/browse/MRELEASE-897?redirect=false)** and commented

In some project multiple versions are used (tomee release = tomee + openejb releases for instance). It is not always possible to split the project in sub projects and then it is not possible to use maven release plugin. Idea would be to support a whitelist of artifacts (a list of patterns would be great).

```

org.superbiz.component:*:1.0.1
org.superbiz.component:*:4.5.8

```

For instance or even:

```

org.superbiz.component:*:@major.@minor.@patch
org.superbiz.component:*:(@major + 3).@minor.@patch

```

to avoid to change it for each release.

This of course would imply the CLI to ask for the multiple versions and not only one even when autoSubModules is set to true (it would just group by versions)

---

**Issue Links:**
- [MRELEASE-1003](https://issues.apache.org/jira/browse/MRELEASE-1003) support multiversions release with autoVersionModules=true
(_**"is duplicated by"**_)

Start by tracing the Maven Release Plugin CLI handling and the configuration represented by releaseVersions and autoSubModules. Review the linked duplicate MRELEASE-1003 and the issue discussion before deciding the scope; done would mean supporting multiple release versions and prompting for or grouping them correctly in the CLI.

Written by the indexing model from the issue text.