Unified go.mod to ensure that catalogd and operator-framework use the same go.mod and fix imports

Author: camilamacedo86

.github/workflows/catalogd-crd-diff.yaml

@@ -11,7 +11,7 @@ jobs:
 
       - uses: actions/setup-go@v5
         with:
-          go-version-file: catalogd/go.mod
+          go-version-file: go.mod
 
       - name: Run make verify-crd-compatibility
         working-directory: catalogd

.github/workflows/catalogd-demo.yaml

@@ -18,7 +18,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version-file: "catalogd/go.mod"
+          go-version-file: "go.mod"
       - name: Run Demo Update
         working-directory: catalogd
         run: make demo-update

.github/workflows/catalogd-e2e.yaml

@@ -25,7 +25,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version-file: "catalogd/go.mod"
+          go-version-file: "go.mod"
       - name: Run the upgrade e2e test
         working-directory: catalogd
         run: make test-upgrade-e2e

.github/workflows/catalogd-go-apidiff.yaml

@@ -15,7 +15,7 @@ jobs:
     - name: Set up Go
       uses: actions/setup-go@v5
       with:
-        go-version-file: "catalogd/go.mod"
+        go-version-file: "go.mod"
       id: go
     - name: Run go-apidiff
       working-directory: catalogd

.github/workflows/catalogd-release.yaml

@@ -25,7 +25,7 @@ jobs:
     - name: Install Go
       uses: actions/setup-go@v5
       with:
-        go-version-file: "catalogd/go.mod"
+        go-version-file: "go.mod"
 
     - name: Docker Login
       if: ${{ github.event_name != 'pull_request' }}

.github/workflows/catalogd-sanity.yaml

@@ -24,7 +24,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version-file: "catalogd/go.mod"
+          go-version-file: "go.mod"
       - name: Run lint checks
         working-directory: catalogd
         run: make lint GOLANGCI_LINT_ARGS="--out-format github-actions"

.github/workflows/catalogd-tilt.yaml

@@ -26,7 +26,7 @@ jobs:
     - name: Install Go
       uses: actions/setup-go@v5
       with:
-        go-version-file: catalogd/go.mod
+        go-version-file: go.mod
     - name: Install Tilt
       run: |
         TILT_VERSION="0.33.3"

.github/workflows/catalogd-unit.yaml

@@ -15,7 +15,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version-file: "catalogd/go.mod"
+          go-version-file: "go.mod"
 
       - name: Unit Test
         working-directory: catalogd

.github/workflows/tilt.yaml

@@ -26,7 +26,7 @@ jobs:
       id: get-catalogd-version
       run: |
         cd operator-controller
-        echo "CATALOGD_VERSION=$(go list -mod=mod -m -f "{{.Version}}" github.com/operator-framework/catalogd)" >> "$GITHUB_OUTPUT"
+        echo "CATALOGD_VERSION=$(go list -mod=mod -m -f "{{.Version}}" github.com/operator-framework/operator-controller/catalogd)" >> "$GITHUB_OUTPUT"
     - uses: actions/checkout@v4
       with:
         repository: operator-framework/catalogd

CONTRIBUTING.md

@@ -18,7 +18,7 @@ As you may or may not know, the Operator-Controller project aims to deliver the
 The user experience captured in the OLM V1 PRD introduces many requirements that are best satisfied by a microservices architecture. The OLM V1 experience currently relies on two projects:
 
 - [The Operator-Controller project](https://github.com/operator-framework/operator-controller/), which is the top level component allowing users to specify operators they'd like to install.
-- [The Catalogd project](https://github.com/operator-framework/catalogd/), which hosts operator content and helps users discover installable content.
+- [The Catalogd project](https://github.com/operator-framework/operator-controller/catalogd/), which hosts operator content and helps users discover installable content.
 
 Each of the projects listed above have their own governance, release milestones, and release cadence. However, from a technical perspective, the "OLM V1 experience" matches the experienced offered by the operator-controller project, the top level component which depends on Catalogd.
 
@@ -120,7 +120,7 @@ As discussed earlier, the operator-controller adheres to a microservice architec
 Unsure where to submit an issue?
 
 - [The Operator-Controller project](https://github.com/operator-framework/operator-controller/), which is the top level component allowing users to specify operators they'd like to install.
-- [The Catalogd project](https://github.com/operator-framework/catalogd/), which hosts operator content and helps users discover installable content.
+- [The Catalogd project](https://github.com/operator-framework/operator-controller/catalogd/), which hosts operator content and helps users discover installable content.
 
 Don't worry if you accidentally submit an issue against the wrong project, if we notice that an issue would fit better with a separate project we'll move it to the correct repository and mention it in the #olm-dev slack channel.