Epic: Implement Semver Library into all service-providers for version matching

[n3rdc4ptn]

Understand the Epic

Currently, service-providers perform exact string matching when resolving component versions. This is fragile and limits user flexibility.

By integrating a semver-aware library, service-providers can:

• Match versions using semantic versioning rules (e.g. 1.2.3 satisfies >=1.0.0)
• Support constraint-based filtering (e.g. ^2.0.0, ~1.5.0, >=2.0.0 <3.0.0)
• Handle v/V prefixed versions correctly (e.g. v1.2.3 matches 1.2.3)
• Handle pre-release and build metadata correctly

This aligns with how OCM core already handles versions using Masterminds/semver/v3.

Context / Background

The OCM project uses github.com/Masterminds/semver/v3 for version matching and constraint evaluation.

Relevant usage in OCM:

• api/utils/semverutils/ - sorting and matching utilities
• api/utils/cobrautils/flag/semver_constraint.go - constraint parsing for CLI flags

This library supports standard semver constraints like >=1.2.0, ^2.0.0, ~1.5.0, etc. The service-providers should use the same library for consistency with OCM core.

User Stories or tasks

No response

What is required to accept the Epic as finished.

Placeholder

Dependencies of this Epic

No response

Risks of this Epic

No response

Known Stakeholders of this Epic

No response

Milestone Definitions for this Epic.

No response

Metrics Definition for this Epic.

No response

Any further valuable resources.

No response