update dependencies

[VinozzZ]

• update k8s dependencies
• update porter to v1.0.0-rc.1
• update getporter/magefile to v0.3.2
• remove Debug flag since it's not used
• update build pipeline to use go 1.18

[VinozzZ]

go: downloading get.porter.sh/operator v0.6.0
go: downloading github.com/onsi/gomega v1.20.1
go: downloading github.com/hashicorp/go-hclog v1.2.2
go: downloading github.com/cnabio/cnab-go v0.24.0
go: downloading github.com/onsi/ginkgo/v2 v2.1.4
go: downloading github.com/cespare/xxhash v1.1.0
get.porter.sh/plugin/kubernetes/pkg/kubernetes imports
	get.porter.sh/porter/pkg/plugins imports
	go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc tested by
	go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc.test imports
	google.golang.org/grpc/interop imports
	golang.org/x/oauth2/google imports
	cloud.google.com/go/compute/metadata: ambiguous import: found package cloud.google.com/go/compute/metadata in multiple modules:
	cloud.google.com/go v0.97.0 (/home/yingrong/go/pkg/mod/cloud.google.com/[email protected]/compute/metadata)
	cloud.google.com/go/compute v1.7.0 (/home/yingrong/go/pkg/mod/cloud.google.com/go/[email protected]/metadata)

[carolynvs]

Thanks for figuring out how to get past those weird go mod errors! 👍

[carolynvs]

You don't need to change anything but I wanted to show you a nice improvement to this gh action in their latest v3 release that uses the go version defined in your go.mod and it automatically sets up caching too

- uses: actions/setup-go@v3
   with:
     go-version-file: go.mod
     cache: true
     cache-dependency-path: go.sum