Favor --show-token over --token for whoami

[liggitt]

I badly want to be able to do oc whoami --token=<some-token>, but we made that the long form of oc whoami -t instead.

Deprecate --token and --context in favor of --show-token and --show-context, so in a release we can switch back to using those for building the client

[liggitt]

@deads2k @smarterclayton @fabianofranz

will open a doc PR to sweep in favor of the short flags if this meets with approval

[smarterclayton]

I really hope no one has baked this into their CI flows.

[liggitt]

[test]

[openshift-bot]

Evaluated for origin test up to 2587916

[openshift-bot]

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/9466/)

[deads2k]

I'm strongly in favor of this, even though it will be breaking.

[smarterclayton]

Because -t is common use I'm ok with redefining "--token" but leaving "-t" unchanged.

[liggitt]

sounds good. this PR hides and marks as deprecated --token and --context. I'll queue up removing the overridden behavior in 1.5
[merge]

[openshift-bot]

Evaluated for origin merge up to 2587916

[fabianofranz]

One more use case for my idea of boolean kinda string flag type. :)

--token
--token=<some-token>

[fabianofranz]

@openshift/cli-review

[fabianofranz]

Needs release notes.

[openshift-bot]

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/9528/) (Image: devenv-rhel7_5103)