Refactor: Use `go tool` instead of `go install` when executing internal CLI tools

[koba1t]

About

During development, execute the internal CLI binary without installing it locally, but rather via go tool. Specifically, consolidate the installation and execution of binaries run via makefiles, shell scripts, etc., into a single CLI call through go tool

This eliminates the need to install binaries via go install each time, and can potentially prevent issues like using outdated versions of tools installed in your computer's GOBIN.

How to migrate

• Since each CLI tool is called from shell scripts, go generate, or Makefiles, replace the invocations with go tool BINARY_NAME.
• Locate and remove all instances where CLI tools are being go installed.
• Verify that the CLI can be called

Tools List

in repo tools

• [x] gorepomod https://github.com/kubernetes-sigs/kustomize/pull/5963
• [ ] mdtogo
• [ ] pluginator

external tools

• [ ] golangci-lint
• [ ] mdrip
• [ ] stringer
• [ ] goimports
• [ ] mdtogo
• [ ] addlicense
• [ ] kind
• [ ] controller-gen
• [ ] embedmd
• [ ] go-bindata
• [ ] go-apidiff
• [ ] gh
• [ ] kubeval

[stormqueen1990]

/triage accepted /kind cleanup

[aryasoni98]

I came across this issue and would love to contribute could you please assign it to me?

[koba1t]

Hi @aryasoni98 Thank you for your contribution!

Since this is an issue for planning multiple tool migrations, I intended to create separate sub-issues for each tool. I created a sub-issue for migrating the k8scopy CLI tool and assigned you to it.