[go.mod] Remove erroneous self-referential replace directive

[Copilot]

Description

This PR fixes the MeshKit v0.8.53 upgrade failure from meshery/meshery.

A local development replace directive was accidentally committed to go.mod:

replace github.com/meshery/meshkit => ../meshkit

This breaks module resolution because:

• The Go module proxy cannot resolve relative paths
• Creates a circular self-reference

Notes for Reviewers

Single-line fix removing the erroneous replace directive. No functional code changes.

Signed commits

• Yes, I signed my commits.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• artifacthub.io
  • Triggering command: /tmp/go-build4109909312/b1740/artifacthub.test /tmp/go-build4109909312/b1740/artifacthub.test -test.paniconexit0 -test.gocoverdir=/tmp/go-build4109909312/b1740/gocoverdir -test.timeout=10m0s -test.short=true -test.coverprofile=/tmp/go-build4109909312/b1740/_cover_.out (dns block)
• charts.bitnami.com
  • Triggering command: /tmp/go-build4109909312/b1740/artifacthub.test /tmp/go-build4109909312/b1740/artifacthub.test -test.paniconexit0 -test.gocoverdir=/tmp/go-build4109909312/b1740/gocoverdir -test.timeout=10m0s -test.short=true -test.coverprofile=/tmp/go-build4109909312/b1740/_cover_.out (dns block)
• charts.crossplane.io
  • Triggering command: /tmp/go-build4109909312/b1740/artifacthub.test /tmp/go-build4109909312/b1740/artifacthub.test -test.paniconexit0 -test.gocoverdir=/tmp/go-build4109909312/b1740/gocoverdir -test.timeout=10m0s -test.short=true -test.coverprofile=/tmp/go-build4109909312/b1740/_cover_.out (dns block)
• cloud.google.com
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• cuelang.org
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• dario.cat
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• filippo.io
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• go.googlesource.com
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• go.opentelemetry.io
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• go.uber.org
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• go.yaml.in
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• google.golang.org
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• gopkg.in
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• gorm.io
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• helm.sh
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• k8s.io
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• oras.land
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)
• sigs.k8s.io
  • Triggering command: /update-job-proxy /update-job-proxy (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

From a clone of github.com/meshery/meshery, upgrading to MeshKit v0.8.53 fails.

Example:

github.com/docker/go-metrics: github.com/meshery/[email protected]: verifying go.mod: github.com/meshery/[email protected]/go.mod: reading https://sum.golang.org/lookup/github.com/meshery/[email protected]: 404 Not Found
server response:
not found: github.com/meshery/[email protected]: invalid version: git ls-remote -q https://github.com/meshery/meshkit in /tmp/gopath/pkg/mod/cache/vcs/ed5e762579e0724bed41ca8bab690f891008ba2ce24d0603f9e2462cb438c481: exit status 128:
fatal: unable to access 'https://github.com/meshery/meshkit/': Failed to connect to github.com port 443: Connection refused

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.