Use --short to report kubectl version

[shamsher31]

What this PR does / why we need it:
Before:

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.2", GitCommit:"8b5a19147530eaac9476b0ab82980b4088bbc1b2",
GitTreeState:"clean", BuildDate:"2021-09-15T21:31:32Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192",
GitTreeState:"clean", BuildDate:"2021-05-21T23:01:33Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/amd64"}

After:

$ kubectl version --short
Client Version: v1.22.2
Server Version: v1.21.1

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 #

Additional information

Special notes for your reviewer

[dharmjit]

Thanks @shamsher31 for raising this PR. I am not sure, but is it advised to use kubectl version --short or what the practice is in general.

[shamsher31]

Thanks @shamsher31 for raising this PR. I am not sure, but is it advised to use kubectl version --short or whats the practice is in general.

It helps users get the exact kubectl version which they can quickly copy and past in a bug report. We have used it in a couple of projects. eg: istio/istio#27108 and istio/istio#29213

[dharmjit]

LGTM