Currently COO doesn't set any CSV fields to hint at version that a given version can replace.

https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/how-to-update-operators.md

For z-stream updates we should add skip range from the first y-stream release.

For new y-stream releases we should add a replace field for the previous y-stream.

For major version bumps we (probably) want to upgrade from the last release with the previous major version. Alternatively we could consider the implications for upgrading from any of the previous y-stream releases.

This will need to be implemented in the midstream rendering since the upstream naming differs.