Controll the golang tool used to build/publish build artifacts.

[mkumatag]

/kind cleanup
/area provider/ibmcloud

What steps did you take and what happened:
While addressing this issue #2261, we realized that the project is relying on the Go version from gcb-docker-gcloud to build and ship release artifacts. This approach is incorrect, as the project should have better control over the Go version used for building artifacts. This task has been created to track the necessary improvements.

reference - #2262 (comment)

What did you expect to happen:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Cluster-api version:
• Minikube/KIND version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[Prajyot-Parab]

/assign @mkumatag

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale