Semver template expansion can produce duplicate skips and replaces of the same target, which confuses OLMv0

    100%

    1. with a semver template configured to generate major-version channels and including minor-version bumps, like this example (written as reproducer-semver.yaml):

          schema: olm.semver
          generatemajorchannels: true                
          stable:               
            bundles:        
              - image:  quay.io/jordankeister/test-operator:v1.0.0                
              - image:  quay.io/jordankeister/test-operator:v1.1.0                
              - image:  quay.io/jordankeister/test-operator:v1.1.2                
              - image:  quay.io/jordankeister/test-operator:v1.1.4           
              - image:  quay.io/jordankeister/test-operator:v1.2.0               
              - image:  quay.io/jordankeister/test-operator:v1.2.1
              - image:  quay.io/jordankeister/test-operator:v1.3.0        
              - image:  quay.io/jordankeister/test-operator:v1.4.0     

    2. expand the template via `opm alpha render-template semver reproducer-semver.yaml`
    3. see that in the major-version FBC channels generated, whenever the upgrade graph would cross a minor-version boundary, it includes the previous minor-version's highest patch version as both a 'skips' and 'replaces' link from the next minor-version's highest patch version.


    

    ...
    "entries": [
        {
            "name": "test-operator-v1.0.0"
        },
        {
            "name": "test-operator-v1.1.0"
        },
        {
            "name": "test-operator-v1.1.2"
        },
        {
            "name": "test-operator-v1.1.4",
            "replaces": "test-operator-v1.0.0",
            "skips": [
                "test-operator-v1.0.0",
                "test-operator-v1.1.0",
                "test-operator-v1.1.2"
            ]
        },
    ...

    ...
    "entries": [
        {
            "name": "test-operator-v1.0.0"
        },
        {
            "name": "test-operator-v1.1.0"
        },
        {
            "name": "test-operator-v1.1.2"
        },
        {
            "name": "test-operator-v1.1.4",
            "replaces": "test-operator-v1.0.0",
            "skips": [  
                "test-operator-v1.1.0",
                "test-operator-v1.1.2"
            ]
        },
    ...