Introducing go-install-tool in the Makefile makes it easier to set up the development environment

[forsaken628]

What this PR does / why we need it:
Current development environments use binary tools that are not isolated, which makes switching between projects troublesome and error-prone. We can improve this situation by introducing go-install-tool in the makefile.

alse see:
https://github.com/kubernetes-sigs/kubebuilder/blob/98d03bed2912b2f7adf73aeaf5f64fafa8fd927b/pkg/plugins/golang/v4/scaffolds/internal/templates/makefile.go#L263-L275

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Checklist:

• Docs included if any changes are user facing

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tenzen-y for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This pull request has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

[andreyvelich]

@forsaken628 I apologies that we don't have time to review this improvement. Are we ready to review this PR ?
@Electronic-Waste @helenxie-bit @tenzen-y Please can you help with review of this PR ?

[tenzen-y]

@forsaken628 I apologies that we don't have time to review this improvement. Are we ready to review this PR ? @Electronic-Waste @helenxie-bit @tenzen-y Please can you help with review of this PR ?

I don't think that we should take this approach. Instead of this, we should enforce the fixed version tools to $REPO_DIR/bin directory so that we can use the same version in our local.

Example: https://github.com/kubeflow/training-operator/blob/cbd4ae7bb32164816278fc0e313effc14b5d2161/Makefile#L119-L125