When having operator in e.g. stable-3.0 channel and new operator is available in stable-3.1 channel, user should just switch to stable-3.1 and the operator should be automatically upgraded. It's not happening with our current configuration.

Workaround for tp2 release was to hardcode spec.replaces into CSV. We need to update our csv generation to fix this problem.

Original thought was that this is only affecting tp releases because of the -tp.x suffix but it's happening also in the upstream where we use x.y.z version format.

This problem should be solved in OLMv1 because that uses semver and not just "distance to head of channel"