In multimodule Golang project upgrade-deps script will float current project references

[cardil]

In projects that utilize Go workspaces, we can have the following situation:

// in build/go.mod
module knative.dev/kn-plugin-event/build

require knative.dev/kn-plugin-event v0.0.0

replace knative.dev/kn-plugin-event => ../

When running hack/update-deps.sh --upgrade --release 1.9 that mock version v0.0.0 gets replaced by current version string, like v0.34.1-0.20230130203928-59adc6bd3cf7.

This prevents doing a release because the releaseability job creates a PR to align deps (see example: knative-extensions/kn-plugin-event#261). Even after merger of such PR, another PR is created (see: knative-extensions/kn-plugin-event#262). This prevents the release.

/kind bug

[cardil]

Probably, the buoy logic needs to be adjusted to exclude the current project from floating deps.

hack/library.sh

Line 705 in c7cfcb0

local buoyArgs=(--release ${RELEASE} --domain ${DOMAIN})