Remove dependency on github.com/blang/semver

[m1kola]

Since #374 we have dependency on both github.com/blang/semver and github.com/Masterminds/semver. We introduced github.com/Masterminds/semver so that we can support certain version range syntax (#379).

I believe we should be able to get rid of dependency on github.com/blang/semver. As far as I see, the only place where we use it is here:

operator-controller/internal/catalogmetadata/filter/bundle_predicates.go

Lines 34 to 42 in 05ffd85

	func InBlangSemverRange(semverRange bsemver.Range) Predicate[catalogmetadata.Bundle] {
	return func(bundle *catalogmetadata.Bundle) bool {
	bundleVersion, err := bundle.Version()
	if err != nil {
	return false
	}
	return semverRange(*bundleVersion)
	}
	}

This piece of code was migrated from old entity source code.

And we only use InBlangSemverRange here.

I believe we can replace InBlangSemverRange with InMastermindsSemverRange in this ocassion.

[m1kola]

@tmshort could you please take a look at this issue? I think we can remove github.com/blang/semver, but I have a feeling that I'm missing sometihng. I would really appreciate if you can confirm this or provide some background into why we did not remove InBlangSemverRange in #374/related PR.

[m1kola]

Ah! I see this thread now. We need blang to support olm.package.required :(

Closing this one.

[tmshort]

We can't get rid of blang/semver since it's used to parse bundle versions (olm.package.required). The syntax different between blang and Masterminds is subtle, and we don't want to break bundle version checks.