Stop bumping go directive unless necessitated by other dependencies

@kaovilai ➜ /workspaces/sdk (961a644) $ go mod graph | grep go@1.23.3 | cut -d ' ' -f 2
go@1.23.3
toolchain@go1.23.3
@kaovilai ➜ /workspaces/sdk (961a644) $ go mod graph | grep go@1.23. | grep -v /sdk | cut -d ' ' -f 2
go@1.23.2
go@1.23.1
toolchain@go1.23.3

Per above, this repo go.mod as it currently stands should have go directive of 1.23.2, not 1.23.3.

This repo by itself should not be enforcing minimum on other repositories importing it. Stop spreading "minimum virus"

toolchain version used will be defined outside of go.mod ideally, such as by installing a newer compatible go toolchain to ci/cd/development env.

Failing that, toolchain directive should be used instead of go directive for bumping versions to not cascade minimum versions to importing dependencies.

toolchain directive, in contrast to the go directive, applies only to the current module (the one defined by the go.mod file). It suggests the toolchain to be used when in that very module, and doesn't propagate to other modules.

High profile repos that have removed/reduced minimum go patch version per user requests

• https://github.com/grpc/grpc-go/pull/7831 motivation

Being proactive to prevent following from reoccuring

• https://github.com/kopia/kopia/issues/4292
• https://github.com/vmware-tanzu/velero/issues/8397
• https://github.com/kubevirt/kubevirt-velero-plugin/pull/292#issuecomment-2482634796

Start with go.mod and reproduce the issue's go mod graph commands to compare the repository's go directive with dependency requirements. Review the Go module and toolchain directive behavior, then verify that the module does not impose an unnecessary patch-version minimum on importing modules and that the dependency graph remains valid.