[issue-95] Handle existing bad osgi versions in the repo

If there is a version in the repo already that looks like 1.2-redhat-1 or
1.2.redhat-1, the next osgi compat version increment should be 1.2.0.redhat-2
[maven-release-plugin] rollback the release of pom-manipulation-ext-0.9
Merge pull request #101 from pgier/issue95

[issue-95] Handle existing bad osgi versions in the repo
Merge pull request #102 from rnc/master

Improve comments, tests and handle property format of '1' for osgi
[maven-release-plugin] prepare release pom-manipulation-ext-0.9
[maven-release-plugin] prepare for next development iteration
Add test cases which fail with the current version parser

If the original version string is a 3 part (major, minor, micro) string which is
ivalid OSGi, the version update fails by adding an additional .0
Initial impl of new version parser
Improvements to get/set qualifier suffix

- Formatting fixes
- performance improvement to getQualifier()
- Better handling of qualifier suffixes
First pass of integrating the new version parsing

Replace osgi conversion logic with new version parser
Update a test which previously did fallback, but now works correctly
Improve the version parsing

Make the version parsing logic a bit simpler and more efficient with less looping.
Minor refactor, add one test case
Complete integration of new version parser

Rework some parsing to better handle various edge cases.
Finish changes to VersioningCalculator to use new parser.
Clean up code which is no longer necessary.
Use regex everywhere instead of manual parsing

This makes the code smaller and easier to read.
Fix ITs

Bug in handling of build number for a single project without an initial build number
Merge pull request #103 from pgier/rewrite-version-parsing

Rewrite version parsing
Merge pull request #104 from rnc/master

Improve handling of relative paths in modules