Fixed #1426 : Replace archived org.semver:api with custom SemVer implementation

[HarshMehta112]

Following this checklist to help us incorporate your
contribution quickly and easily:

• Your pull request should address just one issue, without pulling in other changes.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Each commit in the pull request should have a meaningful subject line and body.
  Note that commits might be squashed by a maintainer on merge.
• Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
  This may not always be possible but is a best-practice.
• Run mvn verify to make sure basic checks pass.
  A more thorough check will be performed on your pull request automatically.
• You have run the integration tests successfully (mvn -Prun-its verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

I've gone ahead and applied for the Individual Contributor License Agreement.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
• In any other case, please file an Apache Individual Contributor License Agreement.

Replace archived org.semver:api with custom SemVer implementation

Fixes #1426

What changed

• Removed dependency on the archived org.semver:api library.
• Introduced a custom internal semantic-versioning implementation: renamed class from Version → SemVer, and refactored related version-policy code under maven-release-semver-policy.
• Updated all references, method calls, and tests to use the new SemVer class.
• Existing unit and integration tests updated accordingly and pass successfully.

[elharo]

Good start. This is going to need some thought and discussion. If we can reduce the visibility to package protected that would enable us to release and iterate.

[elharo]

Run 'mvn spotless:apply' to fix these violations.

[HarshMehta112]

@elharo @slawekjaranowski
Could you please clarify how you would like this feature to be implemented? As discussed with @slawekjaranowski, the suggestion was to follow the SemVer 2.0.0 specification (#1426). I also observed that the existing SemVerVersion-related policies and test cases are already aligned with SemVer 2.0.0, and we could potentially use the recommended regular expression provided in the SemVer documentation: https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string.

However, @elharo pointed out that Maven only compatible with SemVer 1.0.0.

Since I am still new to open-source contribution, I am trying to fully understand the intended direction. Could you please advise on the preferred approach so I can proceed accordingly?

Thank you!

[slawekjaranowski]

@elharo @kwin look ok for me