[MRELEASE-1089] Reduce the default tag format to the project version only

**[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** opened **[MRELEASE-1089](https://issues.apache.org/jira/browse/MRELEASE-1089?redirect=false)** and commented

Back in the days when this plugin was written and all ASF Maven-based projects used the ASF Subversion repo, the common practice was to have one trunk/branches/tags for all component groups instead of the common sense to have one dir per project with distinct trunk/branches/tags. This resulted that the ASF diverged from the common practice and basically imposed `{{}project.artifactId}-{project.version{`}} tag format to the entire Java world. With the emerge of Git one can have one project per repo where this approach was pointless anyway.

Proposal: since this is an overhauled practice, it is neither fruitful for Subversion, Git or Mercurial and a prefix which is appended to every tag is redudant, replace this format with the version only like many others do now.

---

**Remote Links:**
- [GitHub Pull Request #122
](https://github.com/apache/maven-release/pull/122)

Start with the Maven release plugin's default tag-format behavior and review Remote Pull Request #122 for the work already associated with this issue. Done means the default tag contains only the project version, without the artifactId prefix, while preserving the stated release behavior.

Written by the indexing model from the issue text.