OLMv1 uses the semver spec to sort bundles by their version in order to select the highest version that matches a user's filter criteria.

The semver spec states in https://semver.org/#spec-item-10 that build metadata MUST be ignored when determining version precedence.

Unfortunately, the registry+v1 bundle spec specifically decided to ignore that aspect of the spec when implementing `olm.substitutesFor`. For registry+v1 bundles, build metadata is considered for precedence with the following rules:
1. It is considered after major, minor, patch, and prerelease
2. When major, minor, patch, and prerelease are the same, build metadata is compared using the prerelease comparison algorithm (see https://semver.org/#spec-item-11)

OLMv1 does not implement this modification to the semver spec for registry+v1 bundles.

Also, if a ClusterExtension specifies a specific version that includes bundle metadata, OLMv1 does not always select that specific version.

4.18

Nearly always (the sort order is non-deterministic, so sometimes the "right" version is chosen)    

When not specifying build metadata in version filter:
    1. Create a cluster extension for package `ansible-automation-platform-operator` with the version set to `2.5.0`
    2. Inspect the ClusterExtension status and find the installed version.


When specifying build metadata in version filter:
    1. Create a cluster extension for package `ansible-automation-platform-operator` with the version set to `2.5.0+0.1727241223`
    2. Inspect the ClusterExtension status and find the installed version.

When not specifying build metadata in version filter:
    The installed version has build metadata that is less than other bundles 2.5.0 bundles


When specifying build metadata in version filter:
    The installed version does not match 2.5.0+0.1727241223

When not specifying build metadata in version filter:
    The installed version has build metadata that is the highest among all other 2.5.0 bundle build metadatas.

When specifying build metadata in version filter:
    The installed version is 2.5.0+0.1727241223

NOTE TO DEVELOPER: We should not propagate this behavior to other bundle formats because it is a violation of the semver spec. The implementation should only apply this logic when comparing between registry+v1 bundles. 

Future bundle formats MUST NOT consider build metadata for precedence purposes.